| To: | "Russell G. Howe" <rhowe@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair unable to repair a corrupt filesystem |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Sun, 23 Feb 2003 15:32:05 -0600 (CST) |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030223081255.GA14077@lithium.sta.man.ac.uk> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Sun, 23 Feb 2003, Russell G. Howe wrote: > xfs_repair on /var appeared to fix at least some things, but there were > clearly still errors. I re-ran xfs_repair and got this output: > > http://rhowe.sfarc.net/xfs_repair_var.txt.gz > > The output appears identical no matter how many times I run xfs_repair. 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 error is suspicious) but start with that and see what happens. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: xfs_repair unable to repair a corrupt filesystem, l.a walsh |
|---|---|
| Next by Date: | Re: been a while before i could get back to this.., Eric Sandeen |
| Previous by Thread: | RE: xfs_repair unable to repair a corrupt filesystem, l.a walsh |
| Next by Thread: | Re: xfs_repair unable to repair a corrupt filesystem, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |