| 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
| ||
|
Message-ID: <20060724090138.C2083275@wobbly.melbourne.sgi.com> Date: Mon, 24 Jul 2006 09:01:38 +1000 From: Nathan Scott <nathans@....com> To: Christian Kujau <evil@...ouse.de> Cc: linux-kernel@...r.kernel.org, xfs@....sgi.com Subject: Re: XFS breakage in 2.6.18-rc1 On Sat, Jul 22, 2006 at 05:27:24PM +0100, Christian Kujau wrote: > On Wed, 19 Jul 2006, Nathan Scott wrote: > > 2.6.18-rc1 should be fine (contains the corruption fix). Did you > > mkfs and restore? Or at least get a full repair run? If you did, > > and you still see issues in .18-rc1, please let me know asap. > > well, at least for me, corruption/errors *started* with 2.6.18-rc1: > ... > I downgraded to 2.6.17.5 and the errors stopped. Now I've upgraded to > 2.6.18-rc2 and see the same errors: > > xfs_da_do_buf: bno 16777216 > dir: inode 24472381 This is an ondisk corruption - downgrading the kernel will not resolve it. The problem must be triggered by a combination of operations on a directory; I'm certain that if you access inode 24472381 on your filesystem on 2.6.17, that it'll shutdown your filesystem too. See the FAQ entry for a description on how to translate inums to paths, and also the repair -n step to detect any corruption ondisk. cheers. -- Nathan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists