https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #53 from Theodore Tso <tytso@xxxxxxx> 2011-04-01 15:09:03 --- Folks who are experiencing this problem might want to try 2.6.38.2. There was a fix that was committed to mainline and backported to the stable kernels that may fix this problem: commit 95f28604a65b1c40b6c6cd95e58439cd7ded3add Author: Jens Axboe <jaxboe@xxxxxxxxxxxx> Date: Thu Mar 17 11:13:12 2011 +0100 fs: assign sb->s_bdi to default_backing_dev_info if the bdi is going away We don't have proper reference counting for this yet, so we run into cases where the device is pulled and we OOPS on flushing the fs data. This happens even though the dirty inodes have already been migrated to the default_backing_dev_info. Reported-by: Torsten Hilbrich <torsten.hilbrich@xxxxxxxxxxx> Tested-by: Torsten Hilbrich <torsten.hilbrich@xxxxxxxxxxx> Cc: stable@xxxxxxxxxx Signed-off-by: Jens Axboe <jaxboe@xxxxxxxxxxxx> Sorry for not responding to this bug sooner, but I've been crazy busy in the last couple of weeks; troubleshooting and discussion was taking place on LKML, and I was pretty sure this wasn't an ext4 specific issue. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
