| 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
| ||
|
Date: Wed, 2 Jun 2010 12:10:01 GMT From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 16081] Data loss after crash during heavy I/O https://bugzilla.kernel.org/show_bug.cgi?id=16081 --- Comment #6 from Eric Sandeen <sandeen@...hat.com> 2010-06-02 12:10:00 --- If a barrier failed outright you'd see a note in dmesg / logs shortly after the mount, FWIW. Anyway you didn't explicitly disable it. Barrier support in dm/lvm is rather new, as well. Just a thought... Capturing a core from the segfaulted e2fsck would help fix -that- bug ... and attaching the output of the fscks might yield a clue as to what is damaged. -Eric -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
Powered by blists - more mailing lists