| Re: [PATCH] ext3: wrong error behavior [message #5970 is a reply to message #5867] |
Tue, 05 September 2006 22:20  |
Eric Sandeen
Messages: 4
Registered: September 2006
|
Junior Member |
|
|
Vasily Averin wrote:
> SWsoft Virtuozzo/OpenVZ Linux kernel team has discovered that ext3 error
> behavior was broken in linux kernels since 2.5.x versions by the following patch:
>
> 2002/10/31 02:15:26-05:00 tytso@snap.thunk.org
> Default mount options from superblock for ext2/3 filesystems
> http://linux.bkbits.net:8080/linux-2.6/gnupatch@3dc0d88eKbV9 ivV4ptRNM8fBuA3JBQ
>
> In case ext3 file system is mounted with errors=continue (EXT3_ERRORS_CONTINUE)
> errors should be ignored when possible. However at present in case of any error
> kernel aborts journal and remounts filesystem to read-only. Such behavior was
> hit number of times and noted to differ from that of 2.4.x kernels.
I've also noticed this differing behavior,
http://marc.theaimsgroup.com/?l=linux-ext4&m=11537696682 1953&w=2
It passed w/o comment. :)
Unless Ted had a specific reason for changing the behavior, 2.4 and 2.6
should probably be brought into line. Calling ext3_commit_super()
before the panic may defeat (some of) the purpose of the panic option,
though, which is to preserve as much state as possible at the time of
the error for later analysis...
-Eric
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
