| 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
| ||
|
Message-ID: <20080804161626.GZ4470@implementation.uk.xensource.com> Date: Mon, 4 Aug 2008 17:16:26 +0100 From: Samuel Thibault <samuel.thibault@...-lyon.org> To: Andreas Schwab <schwab@...e.de> Cc: linux-kernel@...r.kernel.org Subject: Re: ext3 seems to ignore ECC errors Andreas Schwab, le Mon 04 Aug 2008 18:12:54 +0200, a écrit : > Samuel Thibault <samuel.thibault@...-lyon.org> writes: > > > Andreas Schwab, le Mon 04 Aug 2008 17:39:06 +0200, a écrit : > >> Samuel Thibault <samuel.thibault@...-lyon.org> writes: > >> > However, to my surprise Linux (2.6.26) continued to mount the ext3 > >> > filesystem read/write, spitting out a lot of IDE errors. Shouldn't > >> > filesystems remount read-only and let the admin try to save data in such > >> > case? > >> > >> That's a tunable parameter of the filesystem, see tune2fs(8). > > > > Oh, I had assumed it was on by default, hum. But now it reads > > > > Errors behavior: Remount read-only > > > > and I am still getting the same behavior. Indeed after some VFS > > modifications time it gets remounted read-only, but shouldn't that > > happen as soon as possible? > > The block device may do some retries before passing the error on. Sure. But I forgot to mention that after spitting all these write errors, the filesystem remains mounted read-write. Samuel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists