On Thu, Sep 19, 2002 at 02:22:02PM +1000, Nathan Scott wrote:
> Hi,
>
> On Wed, Sep 18, 2002 at 04:23:59PM -1000, Sidik Isani wrote:
> >
> > Anyway, the crash still happens right after "Starting XFS recovery".
> > Please let me know what I should do next...
> >
>
> I seem to remember Steve fixing an endian problem in the log code
> at one point several months ago - this may be what's biting you -
> perhaps you have a little endian number somewhere in the on disk
> log and the new kernel is expecting it is as big endian.
>
> If so, the right thing to do would be to run recovery using the
> old kernel - so first mount, then unmount the filesystem. This
> should complete fine with the old kernel. Then run xfs_repair
> on the filesystem. This will zero out the log in phase 2, so
> you can start afresh. Once you've done those things you should
> be able to mount and use this filesystem with the latest kernel.
Great. That makes perfect sense. I guess it is not reasonable
to expect the kernel itself to repair damage from previous bugs.
Could it help you to have a copy of my log anyway, to at least
make the new kernel detect this corruption in a more elegant way
than crashing? I do see checks in there masking bits for valid
version numbers and all. I wonder why these are not finding it.
Another RAID with totally different data on it does the same thing.
Thanks for solving my problem (well ... I'll let you know soon ;-)
Be seeing you,
- Sidik
|