| 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: <200607190908.30727.s0348365@sms.ed.ac.uk> Date: Wed, 19 Jul 2006 09:08:30 +0100 From: Alistair John Strachan <s0348365@....ed.ac.uk> To: Nathan Scott <nathans@....com> Cc: Torsten Landschoff <torsten@...ian.org>, linux-kernel@...r.kernel.org, xfs@....sgi.com Subject: Re: XFS breakage in 2.6.18-rc1 On Tuesday 18 July 2006 23:57, Nathan Scott wrote: [snip] > > of programs fail in mysterious ways. I tried to recover using xfs_repair > > but I feel that my partition is thorougly borked. Of course no data was > > lost due to backups but still I'd like this bug to be fixed ;-) > > 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. Just out of interest, I've got a few XFS volumes that were created 24 months ago on a machine that I upgraded to 2.6.17 about a month ago. I haven't seen any crashes so far. Assuming I get the newest XFS repair tools on there, what's the disadvantage of repairing versus creating a new filesystem? What special circumstances are required to cause a crash? -- Cheers, Alistair. Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - 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