Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_repair\s+unable\s+to\s+repair\s+a\s+corrupt\s+filesystem\s*$/: 30 ]

Total 30 documents matching your query.

1. xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Sun, 23 Feb 2003 08:12:55 +0000
I'm having some problems with /var on my machine. The machine itself is rather unstable and hangs every few days, but I don't think that is XFS-related. What does concern XFS is the data corruption
/archives/xfs/2003-02/msg00370.html (9,339 bytes)

2. RE: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "l.a walsh" <xfs@xxxxxxxxx>
Date: Sun, 23 Feb 2003 12:57:13 -0800
Seems that xfs_repair isn't very robust -- it doesn't even detect the problem on my disk that causes xfsdump to knock my rootfs offline. -l http://rhowe.sfarc.net/xfs_repair_var.txt.gz The output app
/archives/xfs/2003-02/msg00372.html (10,485 bytes)

3. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Sun, 23 Feb 2003 15:32:05 -0600 (CST)
Russell - try renaming the lost+found/ dir before you re-run repair. Otherswise, it will unlink it and then re-find all those "lost" inodes. I don't think this is the root of the problem (the 990 err
/archives/xfs/2003-02/msg00373.html (8,936 bytes)

4. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 08:59:31 +1100
There was an XFS problem in syncing when remounting read-only (which happens just before reboot), which was fixed earlier this year - it frequently affected /var because that is always very active du
/archives/xfs/2003-02/msg00375.html (10,650 bytes)

5. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Mon, 24 Feb 2003 03:33:09 +0000
Hm, I didn't realise all filesystems were remounted ro, I thought all but / were unmounted and then only / was remounted ro. Oh well you learn something new every day! See http://rhowe.sfarc.net/xfs_
/archives/xfs/2003-02/msg00376.html (10,833 bytes)

6. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Sun, 23 Feb 2003 18:39:41 -0900
they are. perhaps the readonly fix could also affect a plain umount as well. -- Ethan Benson http://www.alaska.net/~erbenson/ Attachment: pgpTFssdJ0jLP.pgp Description: PGP signature
/archives/xfs/2003-02/msg00377.html (9,966 bytes)

7. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 14:48:15 +1100
No, you were right - I should have read your original mail more carefully. Thanks. Its as it seemed & repair is saying - the inode has an incorrect nblocks field for some reason. I will have to do so
/archives/xfs/2003-02/msg00378.html (11,830 bytes)

8. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 16:27:59 +1100
Can you run the same (first) xfs_db command I sent to print out the inode, except change the 2222 to 6296608? I wonder if these two inodes are pointing at the same extents... No, a hard link would be
/archives/xfs/2003-02/msg00380.html (11,272 bytes)

9. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 18:12:37 +1100
Taa. Hmmm, they look like distinct files, with completely disjoint extents (which is good). I'll still try to revisit this locally, but if you don't need to keep them, you should be able to blow thes
/archives/xfs/2003-02/msg00382.html (10,002 bytes)

10. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Mon, 24 Feb 2003 14:08:06 +0000
Hm, OK. I'll try that then. I also have another problem with /home (log corruption causing mount failure), but the emails I sent to the list about that seem to have been caught in limbo for no good r
/archives/xfs/2003-02/msg00389.html (10,297 bytes)

11. xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Sun, 23 Feb 2003 08:12:55 +0000
I'm having some problems with /var on my machine. The machine itself is rather unstable and hangs every few days, but I don't think that is XFS-related. What does concern XFS is the data corruption
/archives/xfs/2003-02/msg00854.html (9,339 bytes)

12. RE: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "l.a walsh" <xfs@xxxxxxxxx>
Date: Sun, 23 Feb 2003 12:57:13 -0800
Seems that xfs_repair isn't very robust -- it doesn't even detect the problem on my disk that causes xfsdump to knock my rootfs offline. -l http://rhowe.sfarc.net/xfs_repair_var.txt.gz The output app
/archives/xfs/2003-02/msg00856.html (10,485 bytes)

13. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Sun, 23 Feb 2003 15:32:05 -0600 (CST)
Russell - try renaming the lost+found/ dir before you re-run repair. Otherswise, it will unlink it and then re-find all those "lost" inodes. I don't think this is the root of the problem (the 990 err
/archives/xfs/2003-02/msg00857.html (8,936 bytes)

14. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 08:59:31 +1100
There was an XFS problem in syncing when remounting read-only (which happens just before reboot), which was fixed earlier this year - it frequently affected /var because that is always very active du
/archives/xfs/2003-02/msg00859.html (10,650 bytes)

15. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Mon, 24 Feb 2003 03:33:09 +0000
Hm, I didn't realise all filesystems were remounted ro, I thought all but / were unmounted and then only / was remounted ro. Oh well you learn something new every day! See http://rhowe.sfarc.net/xfs_
/archives/xfs/2003-02/msg00860.html (10,833 bytes)

16. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Sun, 23 Feb 2003 18:39:41 -0900
they are. perhaps the readonly fix could also affect a plain umount as well. -- Ethan Benson http://www.alaska.net/~erbenson/ Attachment: pgpQn2yy0RFgJ.pgp Description: PGP signature
/archives/xfs/2003-02/msg00861.html (9,966 bytes)

17. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 14:48:15 +1100
No, you were right - I should have read your original mail more carefully. Thanks. Its as it seemed & repair is saying - the inode has an incorrect nblocks field for some reason. I will have to do so
/archives/xfs/2003-02/msg00862.html (11,830 bytes)

18. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 16:27:59 +1100
Can you run the same (first) xfs_db command I sent to print out the inode, except change the 2222 to 6296608? I wonder if these two inodes are pointing at the same extents... No, a hard link would be
/archives/xfs/2003-02/msg00864.html (11,272 bytes)

19. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 24 Feb 2003 18:12:37 +1100
Taa. Hmmm, they look like distinct files, with completely disjoint extents (which is good). I'll still try to revisit this locally, but if you don't need to keep them, you should be able to blow thes
/archives/xfs/2003-02/msg00866.html (10,002 bytes)

20. Re: xfs_repair unable to repair a corrupt filesystem (score: 1)
Author: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Mon, 24 Feb 2003 14:08:06 +0000
Hm, OK. I'll try that then. I also have another problem with /home (log corruption causing mount failure), but the emails I sent to the list about that seem to have been caught in limbo for no good r
/archives/xfs/2003-02/msg00873.html (10,297 bytes)


This search system is powered by Namazu