linux-ext4 - Re: EXT3 way too happy with write errors

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]

Date:	Thu, 18 Dec 2008 09:18:25 -0800
From:	Simon Kirby <sim@...nation.com>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: EXT3 way too happy with write errors

On Thu, Dec 18, 2008 at 06:07:14PM +0100, Jan Kara wrote:

>   Hello,
> 
>   This was quite a long time ago but it seems nobody replied yet :).

Thanks :)

>   What kernel version is this? Originally, we aborted a journal only if

At the time, this was 2.6.26.5.

> we spotted a write error in filesystem metadata. If we spotted an error
> in data, we just complained but continued. This seems to be exactly the
> thing you are hitting. Latest Linus's tree (i.e. 2.6.28-rc5 or so) should
> have the patches that allow tuning the behavior in data=ordered mode - i.e.
> you can tell the filesystem by data_err=abort and data_err=ignore option
> whether it should abort the filesystem or ignore write error in fs data.

Cool, but one question.. Can you think of a case where anyone would ever
want data_err=ignore?

Should this really be a knob?

Simon-
--
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