lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 15 Nov 2018 16:19:06 +0000
Subject: [Bug 201685] ext4 file system corruption

--- Comment #3 from Jason Gambrel ( ---
(In reply to Theodore Tso from comment #2)
> I'm using a 4.19.0 based kernel (with some ext4 patches for the 4.20
> mainline) and I'm not noticing any file system problems.   I'm running a
> Dell XPS 13 with an NVME SSD, and Debian testing as my userspace.
> It's hard to do anything with a "my file system is corrupted" report without
> any kind of reliable reproduction information.   Remember that file system
> corruptions can be caused by any number of things --- buggy device drivers,
> buggy Nvidia binary modules that dereference wild pointers and randomly
> corrupt kernel memory, RAID code if you are using RAID, etc., etc.
> Also, the symptoms reported by Claude and Jason are very different.  Claude
> has reported that a data block in a shared library file has gotten
> corrupted.  Jason has reported that file system metadata corruption.   This
> could very well be coming from different root causes.
> So it's better with these sorts of things to file separate bugs, and to
> include detailed hardware configuration details, kernel configuration,
> dumpe2fs outputs of the file system in question, as well as e2fsck logs.

Thank you for your reply Theodore and I apologize for my unhelpful post.  I am
relatively new to this space so I find your advice very helpful.  If the file
system corruption happens a 3rd time (hopefully it won't), I will post a
separate bug report.  I also wasn't previously aware of dumpe2fs, so I will
provide that helpful information next time. I have also searched to find any
additional logs and it looks like fsck logs the boot info under
/var/logs/boot.log and potentially /var/logs/syslog.  Unfortunately the
information from my last boot requiring fixation had already been overwritten. 
I will keep this in mind for the future.

If it helps, my system uses an i7 with integrated Intel graphics.  I am not
running any proprietary drivers.  No Raid. 500gb SSD. 16gb ram with a 4gb swap
file (not a swap partition).  I have been using ukuu to install mainline
kernels.  I did not change anything else on my system.  When I jumped from
4.18.17 to 4.19.0 this problem first appeared.  Then it occurred again after
updating to 4.19.1.

I'm uncertain as to whether it would be helpful or not, but while trying to
figure out why this happened to me, I came across a post on Ask Ubuntu with a
few others reporting similar problems.  They did provide some debugging
information in their post at:

Again it might be a different problem from what Claude Heiland-Allen is

Thank you very much for your advice and I will try and provide some useful
information including logs in a separate bug report if it happens again.

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists