Submitter : lord Status : open
Assigned Engineer : nb Priority : 2
*Modified Date : 09/19/00 *Modified User : ak
*Modified User Domain : suse.de *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 (ADD)
From: "andi kleen" <ak@xxxxxxx>
Date: Sep 19 2000 04:15:04PM
[pvnews version: 1.71]
==========================
On Tue, Sep 19, 2000 at 11:16:27AM -0700, lord@xxxxxxx wrote:
> The ioctl does appear to be returning reasonable results to user
> space in that they increase as we move down the file in the normal
> case. I have not confirmed that they are actually correct though.
The most likely problem is that they're simply in the wrong unit,
the arithmetic in the macros linvfs_bmap uses to convert looks suspicious.
-Andi
|