From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 211733] New: ext4 file system unrecoverable corruption
Date: Sat, 13 Feb 2021 15:55:11 +0000 [thread overview]
Message-ID: <bug-211733-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=211733
Bug ID: 211733
Summary: ext4 file system unrecoverable corruption
Product: File System
Version: 2.5
Kernel Version: 5.4.0-65-generic
Hardware: i386
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: martrw@yahoo.com
Regression: No
Kubuntu 20.04, two week old installation
500 SATA HDD, 50GiB / partition/ 180GiB /home partition
Dual boot with Win7 on 50GiB partition
Observation:
Was switching between the Win7 OS and Linux with multiple reboots in short
spans of time(<5min). From Linux OS using Dolphin I moved ~5MB document files
from Win7 partition to Linux /home/xxx/Documents directory and rebooted system
to return to Win7. Made changes in Win7 as needed and booted back into Linux.
I noticed the entire Documents directory was missing, about 50GiB files.
Immediately shut down system and booted up Linux on duplicate drive containing
image from about two weeks prior. Made read only image of /home directory from
corrupted drive and placed on external 1 GiB backup drive.
Using R-Linux, extundelete, debugfs no trace of the Documents directory can be
located on the image or the original /home directory. I can see files I
intentionally deleted during normal operations for over a week prior.
fsck, smartctl indicate no disk issues.
I have not tried to reproduce this issue.
This event seems very similar to the one discuss in this link but I have not
been able to locate that particular bug.
https://www.itnews.com.au/news/stable-linux-kernels-hit-by-serious-file-system-bug-320709
I entered bug report on the bugs.kde.org bug tracker(432762) but was told that
the issue is lower level than the Dolphin gui which I was using.
Apologies if this is a duplicate, but I could not find a similar issue on this
tracker.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-02-13 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 15:55 bugzilla-daemon [this message]
2021-02-16 18:30 ` [Bug 211733] ext4 file system unrecoverable corruption bugzilla-daemon
2021-02-17 13:30 ` bugzilla-daemon
2021-02-17 16:37 ` bugzilla-daemon
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=bug-211733-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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).