On 04-Dec-2000 Russell Cattelan wrote:
> Tony Gale wrote:
>
>> But, the filesystem pretty much goes unrecoverable after
>> I am forced to reset the box:
>
> This could be related to other issues.
> First exactly what version of the XFS tree are you running?
> If you are running anything less than current (as of today)
> or the XFS_BETA_4 image, please upgrade immediately.
I was running linux-2.4-xfs cvs from Nov 27. I can't gauge the
stability of xfs if I keep updating it.
I've upgraded to the current cvs + elevator patch now.
>
> There was a corruption problem in all previous version.
> Symptoms of the corruption does sound similar to what
> you are describing.
>
> At this point you will need to run xfs_repair to get your
> file system back, if repair fails let us know hopefully we
> can fix whatever went wrong.
>
xfs_repair seems to sort out the (numerous) problems, although innd
still won't work with the resulting spool. Will have to speak to innd
people about that.
But, xfs_repair does have an annoyance. I like to run fs repair
programs until it reports no problems, but the way xfs_repair
unlinks lost+found, if there are any files in there you always get
disconnected inodes in phase 6.
Thanks
-tony
---
E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
grep me no patterns and I'll tell you no lines.
The views expressed above are entirely those of the writer
and do not represent the views, policy or understanding of
any other person or official body.
|