jbd2: don't abort if flushing file data failed
authorHidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Fri, 1 Aug 2008 02:26:04 +0000 (22:26 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 1 Aug 2008 02:26:04 +0000 (22:26 -0400)
commite9e34f4e8f42177c66754fec1edfd35e70c18f99
tree659e21aa3ea54c7643c0e3112aa3aba54ca7b4cf
parent9c83a923c67df311c467ec956009f0eb4019195d
jbd2: don't abort if flushing file data failed

In ordered mode, the current jbd2 aborts the journal if a file data buffer
has an error.  But this behavior is unintended, and we found that it has
been adopted accidentally.

This patch undoes it and just calls printk() instead of aborting the
journal.  Unlike a similar patch for ext3/jbd, file data buffers are
written via generic_writepages().  But we also need to set AS_EIO
into their mappings because wait_on_page_writeback_range() clears
AS_EIO before a user process sees it.

Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/jbd2/commit.c