http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #112 from Alexey Fisher <bug-track@xxxxxxxxxxxxxxxxx> 2009-10-25 08:58:06 --- I was able to reproduce fs corruption by passing barrier=0, _but_ i can't be sure burriers are disabled for my dm. fstab say, disabled: ~$ grep barr /etc/fstab ----------------------------------------------------------------- /dev/mapper/zwerg_buntu-root_one / ext4 errors=remount-ro,barrier=0 0 1 /dev/sda8 /home ext4 defaults,barrier=0 0 2 ------------------------------------------------------------------- proc say, disabled: $ grep barr /proc/mounts ---------------------------------------------------------- /dev/mapper/zwerg_buntu-root_one / ext4 rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0 /dev/sda8 /home ext4 rw,relatime,barrier=0,data=ordered 0 0 ------------------------------------------------------------- dmesg say, _enabled_: kernel 2.6.31-14-generic ~$ dmesg | grep barr [ 7.063589] EXT4-fs (dm-0): barriers enabled [ 9.365835] EXT4-fs (sda8): barriers disabled kernel 2.6.32-rc5-00011-g2fdc246 [ 9.365835] EXT4-fs (sda8): barriers disabled i know 2.6.32-rc do not printk if barriers are enabled, so i assume they are still enabled. I think this mess with dmesg vs proc should be fixed too. -- Configure bugmail: http://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
