| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 01 Aug 2012 14:51:43 +0700 From: Tomasz Chmielewski <mangoo@...g.org> To: semenko@...detics.net, linux-ext4@...r.kernel.org, semenko@...m.mit.edu, tytso@....edu, djwong@...ibm.com Subject: Re: "Unknown code" error when enabling metadata_csum on ext4 raid1 device On 08/01/2012 02:48 PM, Zheng Liu wrote: >> didn't try the patch yet, but I've noticed the following in dmesg since 3.5: >> >> [69004.637293] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. >> [69004.637330] EXT4-fs warning (device sda1): dx_probe:647: dx entry: limit != root limit >> [69004.637335] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. >> [69004.637365] EXT4-fs warning (device sda1): dx_probe:647: dx entry: limit != root limit >> [69004.637370] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. >> >> >> Could this be related? > > Are these messages printed before you enable metadata_csum feature? I didn't notice them before trying to enable metadata_csum feature. On the other hand, enabling metadata_csum feature was pretty much the first thing I've made after booting to 3.5 kernel on this system, so it could be it changed something. Also, when I do: dumpe2fs -h /dev/sda1|grep metadata_csum I don't see metadata_csum feature anywhere. -- Tomasz Chmielewski http://blog.wpkg.org -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists