Github messages for voidlinux
 help / color / mirror / Atom feed
From: superiums <superiums@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Data loose on lvm after reboot
Date: Fri, 18 Nov 2022 04:04:38 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40589@inbox.vuxu.org> (raw)

[-- 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

             reply	other threads:[~2022-11-18  3:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  3:04 superiums [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40589@inbox.vuxu.org \
    --to=superiums@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).