linux-ext4 - [Bug 12821] filesystem corrupts on heavy I/O

lists.openwall.net		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 linux-cve-announce 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]

Message-Id: <20090305174612.46122108042@picon.linux-foundation.org>
Date:	Thu,  5 Mar 2009 09:46:12 -0800 (PST)
From:	bugme-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 12821] filesystem corrupts on heavy I/O

http://bugzilla.kernel.org/show_bug.cgi?id=12821

------- Comment #2 from ddi@...ex.dk  2009-03-05 09:46 -------
It continually spews messages in syslog while it's powered on, but that's not
exactly "reproduction" I guess.

Tried to find the inode in question with debugfs, it said that this particular
inode does not belong to any file - maybe because the inode contains filesystem
metadata, not file data?  Anyhow, no useful output - probably in no small part
because I have no clue what I'm doing with debugfs ;-)

New kernel: Okay, upgraded to the latest available Ubuntu Server kernel.  Had
to yank the power; the sync would never finish (vmstat says it synced about
1kB/s).  Looks like the filesystem is also super-slow for some reason.

(Possible that a logging daemon was putting error messages in the buffer cache
while the sync got farther and farther behind trying to sync those, not sure. 
Did kill all loggers at one point, but didn't help much.  Hmm.)

It came up with the new kernel, did a fsck, which finished off with "fsck died
with exit status 1".

Will try e2image in a moment..

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html