http://bugzilla.kernel.org/show_bug.cgi?id=13992 Summary: ext3 data=ordered in fstab prevents booting Product: File System Version: 2.5 Kernel Version: 2.6.30.4 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext3 AssignedTo: fs_ext3@xxxxxxxxxxxxxxxxxxxx ReportedBy: rogerx@xxxxxxxxxxxxxxxx Regression: No I ran into a problem when, when setting CONFIG_EXT3_DEFAULTS_TO_ORDERED=n, the system will not complete booting when data=ordered is set on the root filesystem within /etc/fstab. (Can't remember the exact debug output as I've been muddling over possible e100.c system freezes.) Some work quick hacks that may help resolve are, fsck the filesystem and removing the filesystem option from the /etc/fstab file. This will likely occur with people upgrading from 2.6.29 to 2.6.30 with the data=ordered filesystem option set in fstab. (I personally like a more stable filesystem, so I've set CONFIG_EXT3_DEFAULTS_TO_ORDERED=y due a more severe bug I was tracking down in 2.6.30 concerning e100.c) -- 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
