xfs
[Top] [All Lists]

Re: XFS latest changes, sb corruption?

To: Eric Sandeen <sandeen@xxxxxxx>, Paul Blazejowski <paulb@xxxxxxxxxxxxxxxxxxx>
Subject: Re: XFS latest changes, sb corruption?
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Sun, 24 Mar 2002 20:11:51 +0100
Cc: <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.33.0203241259220.379-100000@xxxxxxxxxxxxxxxxxxx i.com>
References: <20020324172512.5F09122998@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 13:02 24-3-2002 -0600, Eric Sandeen wrote:
On Sun, 24 Mar 2002, Paul Blazejowski wrote:

> Yes, my LILO resides on /dev/sda2 which is the root partition with XFS
> filesystem.And i've been doing that for past 2 years or so without any
> problems.My MBR has NTLOADER and to avoid conflicts with it, i choose to use
> lilo on my / partition.
>
> LILO version is 21.7.5 that shipped with Slackware 8.0.It always worked and i
> knew about the FAQ entry but it never applied in my case until recently.My
> guess is that there's been either a change in XFS or LILO that don't play
> together anymore and i get corrupted superblock on my root....Any comments?

My only comment is that I don't know how this ever worked... if it did, I
think you were just lucky.  :)  The XFS superblock signature / magic
number should be "XFSB" in the first 4 bytes on the partition, and they're
not there in your image - lilo has overwritten it.  I'm afraid that
you'll have to find another way to boot, XFS and lilo want to put data in
the same place.

He could try putting it onto the swap partition.

Cheers

--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.


<Prev in Thread] Current Thread [Next in Thread>