xfs
[Top] [All Lists]

[Fwd: lilo-xfs patch]

To: Linux XFS <linux-xfs@xxxxxxxxxxx>
Subject: [Fwd: lilo-xfs patch]
From: Derek James Witt <djw@xxxxxxxxxxxxxx>
Date: 25 Mar 2002 15:38:20 -0600
Sender: owner-linux-xfs@xxxxxxxxxxx
-- 
**  Derek J Witt                                              **
*   Email: mailto:djw@xxxxxxxxxxxxxx                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **
--- Begin Message ---
To: Derek James Witt <djw@xxxxxxxxxxxxxx>
Subject: lilo-xfs patch
From: Derek James Witt <djw@xxxxxxxxxxxxxx>
Date: 25 Mar 2002 15:26:32 -0600
In-reply-to: <1017080744.2172.6.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20020324075637.4021C5C268@xxxxxxxxxxxxxxxxxxxxx> <1016971074.7957.2.camel@mdew> <1017080744.2172.6.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Hey, everyone. I just hacked up a quick patch for lilo to behave
correctly with XFS.  This just checks the file system type of the
current root partition.  If XFS is detected, lilo aborts with an error.
I also included a -F parameter to force XFS to install on XFS
partitions. Let me know how this looks.

On Mon, 2002-03-25 at 12:25, Derek James Witt wrote:
> Hi, there. I got the same behavior.  I found LILO does overwrite the XFS
> superblock. Evidently, XFS's superblock even includes the boot sector.
> So, could lilo be modified not to run on a XFS root partition?  I can
> try to modify lilo to include a XFS-detection routine and abort if XFS
> is detected on root. I could also put in a parameter to override this
> (if anyone would be bold enough to overwrite the SB).
> On Sun, 2002-03-24 at 05:57, mdew wrote:
> > Yeah I've checkout the CVS, and indeed its br0k3n... same Problem.
> > 
> > Debian Sid+Preemptive+GCC 3.0.4
> > 
> > Once repairing the drive, its bootable again.
> > 
> > 
> > On Sun, 2002-03-24 at 19:56, Paul Blazejowski wrote:
> > > Hi Eric,
> > > 
> > > I have a bug i think...i was able to reproduce the sb corruption after
> > > compiling new kernel.
> > > 
> > > Updated my xfs tree with todays CVS (no changes) then i generated a diff 
> > > against clean 2.4.18 kernel patched with xfs and jfs patches,did make dep 
> > > then make bzImage followed by make modules...all of these steps went fine.
> > > I rerun /sbin/lilo to update the loader and made a quick boot disk using:
> > > dd if=/dev/sda2 of=/dev/fd0 ibs=1440 count=1 (sda2 is the partition with 
> > > xfs).
> > > Again there was no crashes or forced shutdowns...rebooted the box and 
> > > when 
> > > new kernel booted it showed these errors: 
> > > 
> > > XFS: bad magic number
> > > XFS: SB validate failed
> > > VFS: unable to mount block device on (8,2) or something close.
> > > 
> > > Again this is on Slackware Linux 8.0 with kernel 2.4.18 and gcc 2.95.3.
> > > 
> > > This is what xfs_repair shows:
> > > 
> > > xfs_repair -n /dev/sda2
> > > Phase 1 - find and verify superblock...
> > > bad primary superblock - bad magic number !!!
> > > 
> > > attempting to find secondary superblock...
> > > ...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!
> > ..!
> > > ....................found 
> > > candidate secondary superblock...
> > > verified secondary superblock...
> > > would write modified primary superblock
> > > primary superblock would have been modified.
> > > cannot proceed further in no_modify mode.
> > > exiting now.
> > > 
> > > I did not make any changes to the fs yet...how would i pull the first few 
> > > kb 
> > > off of the fs you mentioned earlier? Thanks again for your help.
> > > 
> > > Regards,
> > > 
> > > Paul
> > >  
> > -- 
> > ph33r!
> > Linux mdew 2.4.18-xfs-preemptive #4 Sun Mar 24 21:44:59 NZST 2002 i686
> > unknown
> > 
> -- 
> **  Derek J Witt                                              **
> *   Email: mailto:djw@xxxxxxxxxxxxxx                           *
> *   Home Page: http://www.flinthills.com/~djw/                 *
> *** "...and on the eighth day, God met Bill Gates." - Unknown **
-- 
**  Derek J Witt                                              **
*   Email: mailto:djw@xxxxxxxxxxxxxx                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

Attachment: lilo-xfs.diff
Description: Text document

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part

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