Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*power\s+failure\s+\.\.\s+broken\s+files\.\.\s+broken\s+FS\s+\:\(\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*power\s+failure\s+\.\.\s+broken\s+files\.\.\s+broken\s+FS\s+\:\(\.\s*$/: 24 ]

Total 24 documents matching your query.

21. Re: power failure .. broken files.. broken FS :(. (score: 1): Author: Daniel Palmer <danielpalmer@xxxxxxxxxxxxx>; Date: Mon, 05 Jan 2004 21:02:49 +0000; 2.6.0(-1) .. I think, that's the version apt says it is. Cheers, Daniel Palmer; /archives/xfs/2004-01/msg00811.html (8,775 bytes)
22. Re: power failure .. broken files.. broken FS :(. (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Mon, 5 Jan 2004 17:27:39 -0600 (CST); ... ... ... That looks a little odd, repair can't seem to decide how many blocks that inode should have, waffling between 8 and 0. does the -v option give you any more interesting info? how big is th; /archives/xfs/2004-01/msg00813.html (9,261 bytes)
23. Re: power failure .. broken files.. broken FS :(. (score: 1): Author: Daniel Palmer <danielpalmer@xxxxxxxxxxxxx>; Date: Tue, 06 Jan 2004 00:29:45 +0000; rei:/# xfs_repair -v /dev/hdb1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... zero_log: head block 6687 tail block 6687 - scan filesystem freespace and inode maps; /archives/xfs/2004-01/msg00815.html (13,050 bytes)
24. Re: power failure .. broken files.. broken FS :(. (score: 1): Author: Brian Knotts <bknotts@xxxxxxxxxxxxxxxxx>; Date: Wed, 21 Jan 2004 22:27:23 -0800; I am having the same problem with a file on one of my partitions. Interestingly, I am also running debian sid. In addition to the same stuff you are getting back from xfs_repair, I get this in the sy; /archives/xfs/2004-01/msg01006.html (8,864 bytes)

Current List: 21 - 24
Page: [1] [2]