• Hidehiro Kawai's avatar
    ext3: add an option to control error handling on file data · 0e4fb5e2
    Hidehiro Kawai authored
    If the journal doesn't abort when it gets an IO error in file data blocks,
    the file data corruption will spread silently.  Because most of
    applications and commands do buffered writes without fsync(), they don't
    notice the IO error.  It's scary for mission critical systems.  On the
    other hand, if the journal aborts whenever it gets an IO error in file
    data blocks, the system will easily become inoperable.  So this patch
    introduces a filesystem option to determine whether it aborts the journal
    or just call printk() when it gets an IO error in file data.
    
    If you mount a ext3 fs with data_err=abort option, it aborts on file data
    write error.  If you mount it with data_err=ignore, it doesn't abort, just
    call printk().  data_err=ignore is the default.
    Signed-off-by: default avatarHidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
    Cc: Jan Kara <jack@ucw.cz>
    Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    0e4fb5e2
ext3_fs.h 29.7 KB