Bug#319002: e2fsprogs: tune2fs -O +has_journal on a mounted fs created a corrupt fs

2005-07-22 Thread Theodore Ts'o
On Tue, Jul 19, 2005 at 05:43:43PM -0400, Ariel wrote: > > Is there any combination of inode parameters that could cause this? (i.e. > fsck needs to be run twice, never mind how the fs got there?) It looks to > my uneducated eye that the only real error is that i_links_count was 0 > instead of

Bug#319002: e2fsprogs: tune2fs -O +has_journal on a mounted fs created a corrupt fs

2005-07-19 Thread Ariel
On Tue, 19 Jul 2005, Theodore Ts'o wrote: On Tue, Jul 19, 2005 at 02:46:42AM -0400, Ariel wrote: Package: e2fsprogs Version: 1.37-2 Severity: important This was running on a system with a ro / fs changed via remount to rw. (So /etc/mtab was not real, since nothing rewrote it afterward.) I don

Bug#319002: e2fsprogs: tune2fs -O +has_journal on a mounted fs created a corrupt fs

2005-07-19 Thread Theodore Ts'o
On Tue, Jul 19, 2005 at 02:46:42AM -0400, Ariel wrote: > Package: e2fsprogs > Version: 1.37-2 > Severity: important > > This was running on a system with a ro / fs changed via remount to rw. > (So /etc/mtab was not real, since nothing rewrote it afterward.) > I don't know if this is relevant - sin

Bug#319002: e2fsprogs: tune2fs -O +has_journal on a mounted fs created a corrupt fs

2005-07-19 Thread Ariel
Package: e2fsprogs Version: 1.37-2 Severity: important This was running on a system with a ro / fs changed via remount to rw. (So /etc/mtab was not real, since nothing rewrote it afterward.) I don't know if this is relevant - since I did the exact same thing in the same session to another fs, and