Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*bad\s+fs\s+\-\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*bad\s+fs\s+\-\s+xfs_repair\s+3\.01\s+crashes\s+on\s+it\s*$/: 8 ]

Total 8 documents matching your query.

1. bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Fri, 3 Jul 2009 13:20:43 +0200; Tonight our server rebooted, and I found in /var/log/warn that he was crying a lot about xfs since June 7 already: Jun 7 03:06:31 orion.i.zmi.at kernel: Filesystem "dm-0": corrupt inode 3857051697 ((; /archives/xfs/2009-07/msg00025.html (10,378 bytes)
2. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 03 Jul 2009 13:34:48 -0500; ... I'll have to think about why this didn't shut down the fs. There are just a few that don't. Thanks for the metadump image, I'll try to take a look. -Eric; /archives/xfs/2009-07/msg00031.html (8,885 bytes)
3. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Sat, 04 Jul 2009 00:43:02 -0500; ... ok yeah we should see why fsr didn't print anything ... Ok, so this is essentially some code which first does a scan; if it finds an error it bails out and clears the inode, but if not, it calls; /archives/xfs/2009-07/msg00033.html (9,474 bytes)
4. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Sun, 12 Jul 2009 19:02:28 +0200; Who's that? Any ideas/news on this? I'd like to xfs_repair that stuff. It seems to only hit one file, but I don't dare delete it, maybe it makes things worse? mfg zmi -- // Michael Monnerie, Ing.BSc; /archives/xfs/2009-07/msg00104.html (8,714 bytes)
5. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Sun, 12 Jul 2009 13:09:48 -0500; The ex-sgi xfs_repair maintainer :) Sorry, I will get back to this soon - today I hope. I seem to be getting more and more familiar w/ xfs_repair these days. :) If you do want to try deleting that on; /archives/xfs/2009-07/msg00105.html (9,342 bytes)
6. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Sun, 12 Jul 2009 13:52:20 -0500; Hm, the other sort of interesting thing here is that a recently-reported RH bug: [Bug 510823] "Structure needs cleaning" when reading files from an XFS partition (extent count for ino XYZ data fork t; /archives/xfs/2009-07/msg00106.html (9,103 bytes)
7. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Mon, 13 Jul 2009 00:08:20 +0200; find: "./samba/tmp/BettyPC.tib": Die Struktur muss bereinigt werden (means: structure needs cleaning) I'm not sure if that message means that file has the corresponding inode number? If it is, it's a; /archives/xfs/2009-07/msg00107.html (17,514 bytes)
8. Re: bad fs - xfs_repair 3.01 crashes on it (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Mon, 31 Aug 2009 08:40:35 +0200; To warm up the old thread, I did this now: * make metadump * mount it * remove unneeded files/dirs This already produced lots of errors, where files/dirs couldn't be deleted. I made a metadump of thi; /archives/xfs/2009-08/msg00379.html (23,308 bytes)

Current List: 1 - 8
Page: [1]