Submitter : lord *Status : closed
Assigned Engineer : lord *Fixed By : lord
*Fixed By Domain : sgi.com *Closed Date : 09/20/00
Priority : 2 *Modified Date : 09/20/00
*Modified User : lord *Modified User Domain : sgi.com
*Fix Description :
From: steve lord <lord@xxxxxxx> (TAKE)
Date: Sep 20 2000 12:00:09PM
[pvnews version: 1.71]
----------------------------
Two bugs in here, the map file has always just been written when we ask
for its disk location, so it tends to be delalloc. Flush files which are
delalloc.
Secondly, the return value from xfs_bmapi was being interpreted badly. It
did not take into account the fact that the extent returned could start
at a different file offset than we queried for.
Date: Wed Sep 20 11:54:51 PDT 2000
Workarea: jen.americas.sgi.com:/src/lord/xfs-clean
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.0-test1-xfs
Modid: 2.4.0-test1-xfs:slinx:74735a
linux/fs/xfs/linux/xfs_iops.c - 1.69
- in linvfs_bmap ensure that a file has a disk location before
attempting
to find it - flush delalloc files. Then in doing the block
calculations
take into account the difference between the start of the extent
returned
and the location we were asking for.
Description :
Running lilo to install a kernel from an xfs filesystem does not
work. It generates a corrupt lilo map file - booting the system
results in a prompt of LIL- and a hung machine which requires a
rescue disk to get running again.
Lilo installs some code in the boot area of a disk which is used
to indicate where the kernel lives on disk. When running it uses
the FIBMAP ioctl to determine the disk location of the kernel
this is recorded into a map file. The location of the map file
is then recorded into the boot area of the disk.
.....
==========================
ADDITIONAL INFORMATION (REASSIGN)
From: lord@xxxxxxx (BugWorks)
Date: Sep 20 2000 11:52:37AM
==========================
I have a fix
|