| 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: Thu, 20 Jul 2006 00:51:22 -0500 From: Jeffrey Hundstad <jeffrey.hundstad@...u.edu> To: Nathan Scott <nathans@....com> Cc: Mattias Hedenskog <ml@...og.se>, linux-kernel@...r.kernel.org, xfs@....sgi.com Subject: Re: XFS breakage in 2.6.18-rc1 Nathan Scott wrote: > On Wed, Jul 19, 2006 at 09:59:33AM -0500, Jeffrey E. Hundstad wrote: > >> I did try the xfs_repair 2.8.4 for a volume running on 2.6.17.4 and it >> annihilated the volume. This volume was not showing signs of crashing. >> So... I guess I would certainly not run xfs_repair unless there is good >> reason. >> > > Erm, wha..? Can you expand on "annihilated" a bit? (please send > me the full xfs_repair output if you still have it). > Nathan Scott, I'm very sorry; I don't have the output anymore. By annihilated I mean that there were several directories trees that /didn't work/. If you tried to cd into the directory or take a directory listing... or used a file that you knew was in these certain directories then you'd get pages of debug message to the console; and no usable data. I re-ran xfs_repair and retried several times but the condition never seemed to improve or get worse for that matter. I /incorrectly/ figured it was a known issue or I'd have saved the output. Sorry again. -- Jeffrey Hundstad - 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