On Tue, May 07, 2002 at 03:13:12PM -0500, Stephen Lord wrote:
> >Is there something we can test in the meantime to get our filesystem
> >back? I was thinking of commenting out the zero_log() part of xfs_repair
> >to get it to run the rest of the process. Is that safe? Will the
> >filesystem mount afterwards?
>
> Can you run xfs_check on the filesystem and see what that reports? It
> ignores the log,
> so there is no problem there.
It ignores the log, but reports 152558 other errors...
That sounds like a lot....
> You can then use dd to write some zeros into this location, you probably
> want to do it for logblocks blocks, this value is in 4K units, just multiply
> by 8 to get 512 byte units.
>
> To be doubly safe, dd this portion of the device out to a file before
> zeroing it.
>
> You can then use xfs_repair on the filesystem to hopefully fix it up,
> it usually does a good job.
Thanks.
I will try this if we can not get xfs_repair to fix the problem, but
right now I think we're close to locating the problem and then it would
be better to fix it so we don't run into this again.
I've copied the log into a file; let me know if you want a copy to find
out why it got corrupted in the first place... (it used to run
2.4.9-13SGI_XFS_1.0.2 kernel, so it maybe the bug is fixed already?)
--
Ragnar Kjørstad
Big Storage
|