* [ISSUE] Data loose on lvm after reboot
@ 2022-11-18 3:04 superiums
2022-11-19 20:17 ` ahesford
` (16 more replies)
0 siblings, 17 replies; 18+ messages in thread
From: superiums @ 2022-11-18 3:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
New issue by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589
Description:
i have two ext4 logical volum, one normal, one with luks crypt.
one day i found all data on luks lost. but the lv can be mounted normally, and fsck found no err.
i reformated it with luksFormat and mkfs.ex4. then tried seral times to write, and found:
- before reboot, everything goes right. write ok, read ok, size ok.
- after reboot, everything has gone, even folders, the volum seems newly formatted.
- even exec `sync ` command, everything lost after reboot most time, only once the folder was kept.
- if write in arch instead of voidLinux, the files was kept , could be seen in both arch and void.
- if write something in voidLinux again, write ok, read ok, but after reboot, everything lost., **including the existing files**.
- fsck found no err.
all these situation happens in both luks lv and normal lv.
## additional
- my void system and home was also on lvm, but never loose.
- the normal lv which loose data was newly formatted in void. before this action, it works ok in other system.
- these volum was mounted manually without fstab.
## versions
- void linux, kernel 5.19.17_1
- wayland
- wayfire 0.7.3
- thunar 4.6.11
- foot 1.13.1
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
@ 2022-11-19 20:17 ` ahesford
2022-11-20 9:11 ` superiums
` (15 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ahesford @ 2022-11-19 20:17 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1320961246
Comment:
You should probably post your `/etc/crypttab` and clarify what you mean by "mount point i usually use `/dev/shm/xxx`". None of your physical disks or LVM devices should be in `/dev/shm`.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
2022-11-19 20:17 ` ahesford
2022-11-20 9:11 ` superiums
@ 2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
` (13 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-20 9:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321076543
Comment:
> You should probably post your `/etc/crypttab` and clarify what you mean by "mount point i usually use `/dev/shm/xxx`". None of your physical disks or LVM devices should be in `/dev/shm`.
i mean i usually do like this:
```
sudo mount /dev/mapper/vg-lv3 /dev/shm/lv3
```
sorry for my unclear description.
my lv was not listed in `/etc/crypttab`
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
2022-11-19 20:17 ` ahesford
@ 2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
` (14 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-20 9:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321076542
Comment:
> You should probably post your `/etc/crypttab` and clarify what you mean by "mount point i usually use `/dev/shm/xxx`". None of your physical disks or LVM devices should be in `/dev/shm`.
i mean i usually do like this:
```
sudo mount /dev/mapper/vg-lv3 /dev/shm/lv3
```
my lv was not listed in `/etc/crypttab`
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (2 preceding siblings ...)
2022-11-20 9:11 ` superiums
@ 2022-11-20 9:11 ` superiums
2022-11-20 12:36 ` ahesford
` (12 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-20 9:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321076542
Comment:
> You should probably post your `/etc/crypttab` and clarify what you mean by "mount point i usually use `/dev/shm/xxx`". None of your physical disks or LVM devices should be in `/dev/shm`.
i mean i usually do like this:
```
sudo mount /dev/mapper/vg-lv3 /dev/shm/lv3
```
my lv was not listed in `/etc/crypttab`
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (3 preceding siblings ...)
2022-11-20 9:11 ` superiums
@ 2022-11-20 12:36 ` ahesford
2022-11-21 7:06 ` superiums
` (11 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ahesford @ 2022-11-20 12:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321122125
Comment:
Why are you mounting things under `/dev/shm`? That's ill advised.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (4 preceding siblings ...)
2022-11-20 12:36 ` ahesford
@ 2022-11-21 7:06 ` superiums
2022-11-21 8:32 ` sgn
` (10 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-21 7:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321549194
Comment:
> Why are you mounting things under `/dev/shm`? That's ill advised.
aha, got it ! this is the reason which caused the issue.
i've tried to mount lv to /media/xxx, and it never loose now.
i mount it to /dev/shm/xxx for temp use, usuallay i use /dev/shm as temp directory.
before use void linux, in arch, there's no problem in this way.
but seems in voidLinux it works in different way from other os .
i'm now interesting with why mount to /dev/shm/xxx will cause data loose.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (5 preceding siblings ...)
2022-11-21 7:06 ` superiums
@ 2022-11-21 8:32 ` sgn
2022-11-21 13:02 ` [ISSUE] [CLOSED] " ahesford
` (9 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2022-11-21 8:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1321689212
Comment:
Do you have `elogind` installed and enabled?
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [ISSUE] [CLOSED] Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (6 preceding siblings ...)
2022-11-21 8:32 ` sgn
@ 2022-11-21 13:02 ` ahesford
2022-11-21 13:02 ` ahesford
` (8 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ahesford @ 2022-11-21 13:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Closed issue by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589
Description:
i have two ext4 logical volum, one normal, one with luks crypt.
one day i found all data on luks lost. but the lv can be mounted normally, and fsck found no err.
i reformated it with luksFormat and mkfs.ex4. then tried seral times to write, and found:
- before reboot, everything goes right. write ok, read ok, size ok.
- after reboot, everything has gone, even folders, the volum seems newly formatted.
- even exec `sync ` command, everything lost after reboot most time, only once the folder was kept.
- if write in arch instead of voidLinux, the files was kept , could be seen in both arch and void.
- if write something in voidLinux again, write ok, read ok, but after reboot, everything lost., **including the existing files**.
- fsck found no err.
all these situation happens in both luks lv and normal lv.
## additional
- my void system and home was also on lvm, but never loose.
- the normal lv which loose data was newly formatted in void. before this action, it works ok in other system.
- these volum was mounted manually without fstab.
- i usually mount volums to /dev/shm/xxx
## versions
- void linux, kernel 5.19.17_1
- wayland
- wayfire 0.7.3
- thunar 4.6.11
- foot 1.13.1
- lvm2-2.02.187_2
- libllvm12-12.0.1_4
- cryptsetup-2.5.0_1
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (7 preceding siblings ...)
2022-11-21 13:02 ` [ISSUE] [CLOSED] " ahesford
@ 2022-11-21 13:02 ` ahesford
2022-11-21 14:58 ` ahesford
` (7 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ahesford @ 2022-11-21 13:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1322033667
Comment:
`/dev/shm` is used by the shared-memory interface and not intended for direct use by users. In general, you should never mount thing inside `/dev`.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (8 preceding siblings ...)
2022-11-21 13:02 ` ahesford
@ 2022-11-21 14:58 ` ahesford
2022-11-22 14:00 ` superiums
` (6 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ahesford @ 2022-11-21 14:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1322033667
Comment:
~~`/dev/shm` is used by the shared-memory interface and not intended for direct use by users.~~ In general, you should never mount thing inside `/dev`.
Edit: turns out `/dev/shm` is just a tmpfs mount and is intended for users to store things guaranteed not to be on disk (this seems like a poorly developed concept, because you shouldn't expect any particular storage behavior based solely on where you save and read files), but that has no bearing on the recommendation against mounting things under `/dev/`
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (9 preceding siblings ...)
2022-11-21 14:58 ` ahesford
@ 2022-11-22 14:00 ` superiums
2022-11-22 14:00 ` superiums
` (5 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-22 14:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1323723532
Comment:
> Do you have `elogind` installed and enabled?
yes , elogind was installed, and started.
but the service was not enabled.
maybe started by greetd.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (10 preceding siblings ...)
2022-11-22 14:00 ` superiums
@ 2022-11-22 14:00 ` superiums
2022-11-22 14:01 ` superiums
` (4 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-22 14:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1323723547
Comment:
> Do you have `elogind` installed and enabled?
yes , elogind was installed, and started.
but the service was not enabled.
maybe started by greetd.
> ~`/dev/shm` is used by the shared-memory interface and not intended for direct use by users.~ In general, you should never mount thing inside `/dev`.
>
> Edit: turns out `/dev/shm` is just a tmpfs mount and is intended for users to store things guaranteed not to be on disk (this seems like a poorly developed concept, because you shouldn't expect any particular storage behavior based solely on where you save and read files), but that has no bearing on the recommendation against mounting things under `/dev/`
thank you very much!
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (11 preceding siblings ...)
2022-11-22 14:00 ` superiums
@ 2022-11-22 14:01 ` superiums
2022-11-22 14:13 ` sgn
` (3 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-22 14:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1323723547
Comment:
> ~`/dev/shm` is used by the shared-memory interface and not intended for direct use by users.~ In general, you should never mount thing inside `/dev`.
>
> Edit: turns out `/dev/shm` is just a tmpfs mount and is intended for users to store things guaranteed not to be on disk (this seems like a poorly developed concept, because you shouldn't expect any particular storage behavior based solely on where you save and read files), but that has no bearing on the recommendation against mounting things under `/dev/`
thank you very much!
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (12 preceding siblings ...)
2022-11-22 14:01 ` superiums
@ 2022-11-22 14:13 ` sgn
2022-11-23 4:47 ` superiums
` (2 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2022-11-22 14:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1323743426
Comment:
`/dev/shm` is for SHared Memory IPC, it will be cleaned up up on logging out. https://github.com/systemd/systemd/issues/2039
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (13 preceding siblings ...)
2022-11-22 14:13 ` sgn
@ 2022-11-23 4:47 ` superiums
2022-11-23 4:49 ` superiums
2022-11-23 7:33 ` sgn
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-23 4:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1324544967
Comment:
> `/dev/shm` is for SHared Memory IPC, it will be cleaned up up on logging out. [systemd/systemd#2039](https://github.com/systemd/systemd/issues/2039)
yeh, files in it will be cleaned.
but mount device to it , data is not saved in it.
in arch , no data will loose if do the same thing.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (14 preceding siblings ...)
2022-11-23 4:47 ` superiums
@ 2022-11-23 4:49 ` superiums
2022-11-23 7:33 ` sgn
16 siblings, 0 replies; 18+ messages in thread
From: superiums @ 2022-11-23 4:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1324544967
Comment:
> `/dev/shm` is for SHared Memory IPC, it will be cleaned up up on logging out. [systemd/systemd#2039](https://github.com/systemd/systemd/issues/2039)
yeh, files in it will be cleaned.
but mount device to it , data is not saved in it.
in arch and ubuntu , no data will loose if do the same thing.
maybe the mount options differs from each other.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Data loose on lvm after reboot
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
` (15 preceding siblings ...)
2022-11-23 4:49 ` superiums
@ 2022-11-23 7:33 ` sgn
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2022-11-23 7:33 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1324654532
Comment:
Noone care if it's a normal directory or mount-point:
https://github.com/systemd/systemd/blob/d9338387d94ad611233cf0753801eefccfda432a/src/shared/clean-ipc.c#L221-L300
Re: arch and Ubuntu, I don't know your configuration, I can't comment.
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2022-11-23 7:33 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-18 3:04 [ISSUE] Data loose on lvm after reboot superiums
2022-11-19 20:17 ` ahesford
2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
2022-11-20 12:36 ` ahesford
2022-11-21 7:06 ` superiums
2022-11-21 8:32 ` sgn
2022-11-21 13:02 ` [ISSUE] [CLOSED] " ahesford
2022-11-21 13:02 ` ahesford
2022-11-21 14:58 ` ahesford
2022-11-22 14:00 ` superiums
2022-11-22 14:00 ` superiums
2022-11-22 14:01 ` superiums
2022-11-22 14:13 ` sgn
2022-11-23 4:47 ` superiums
2022-11-23 4:49 ` superiums
2022-11-23 7:33 ` sgn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).