ext4/jbd2: Avoid WARN() messages when failing to write to the superblock
This fixes some very common warnings reported by kerneloops.org Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
This commit is contained in:
@ -2810,13 +2810,34 @@ static void ext4_commit_super(struct super_block *sb,
|
||||
|
||||
if (!sbh)
|
||||
return;
|
||||
if (buffer_write_io_error(sbh)) {
|
||||
/*
|
||||
* Oh, dear. A previous attempt to write the
|
||||
* superblock failed. This could happen because the
|
||||
* USB device was yanked out. Or it could happen to
|
||||
* be a transient write error and maybe the block will
|
||||
* be remapped. Nothing we can do but to retry the
|
||||
* write and hope for the best.
|
||||
*/
|
||||
printk(KERN_ERR "ext4: previous I/O error to "
|
||||
"superblock detected for %s.\n", sb->s_id);
|
||||
clear_buffer_write_io_error(sbh);
|
||||
set_buffer_uptodate(sbh);
|
||||
}
|
||||
es->s_wtime = cpu_to_le32(get_seconds());
|
||||
ext4_free_blocks_count_set(es, ext4_count_free_blocks(sb));
|
||||
es->s_free_inodes_count = cpu_to_le32(ext4_count_free_inodes(sb));
|
||||
BUFFER_TRACE(sbh, "marking dirty");
|
||||
mark_buffer_dirty(sbh);
|
||||
if (sync)
|
||||
if (sync) {
|
||||
sync_dirty_buffer(sbh);
|
||||
if (buffer_write_io_error(sbh)) {
|
||||
printk(KERN_ERR "ext4: I/O error while writing "
|
||||
"superblock for %s.\n", sb->s_id);
|
||||
clear_buffer_write_io_error(sbh);
|
||||
set_buffer_uptodate(sbh);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user