[Bug 14354] Bad corruption with 2.6.32-rc1 and upwards

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



http://bugzilla.kernel.org/show_bug.cgi?id=14354





--- Comment #62 from Theodore Tso <tytso@xxxxxxx>  2009-10-16 14:41:45 ---
Alexey, if reinstalling kernel modules is your best reproduction case, are you
seeing actual file system corruption, or simply zero-length files?  And are you
using the "sync" command after re-installing the kernel modules?

If it is actual file system corruption, try mounting the root filesystem with
"auto_da_alloc=0"  That is, add the boot command-line option
"rootflags=auto_da_alloc=0".   This will probably increase the likelihood of
zero-length files if you don't use "sync" after reinstalling the kernel modules
--- this is to be expected, since we are disabling the hueristic used to try to
avoid zero-length files which aren't synced out to disk before an unclean
shutdown.   The goal of this experiment is to see if maybe there's something
about this hueristic which is screwing up the ability to recover the filesystem
free of corruptions after an unclean shutdown.

-- 
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

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux