Hi Eric and Martin,
Thanks for the patch. I saw the boot stuff from a few days ago... and I
also had those problems, but I didn't need to boot with an xfs disk so
just used the rh71 disks to install... I didn't get the connection :)
Should I go ahead and patch the kernel, reboot, then reformat the disk?
Could there be a side effect from having the disk formatted from the old
kernel and using the patched one?
Thanks again, paul
Eric Sandeen wrote:
>
> "Martin K. Petersen" wrote:
> >
> > >>>>> "Paul" == Paul Rossman <pdr@xxxxxxxxxxxxxxxxxxx> writes:
> >
> > Paul> [root@x /]# mkfs.xfs -f /dev/rd/c0d0p1 mkfs.xfs: warning -
> > Paul> cannot set blocksize on block device /dev/rd/c0d0p1
> >
> > This has been fixed in the current CVS tree.
> >
> > Eric Sandeen has an updated driver disk containing a workaround for
> > the 1.0 release.
>
> Hi Paul -
>
> Looks like you're already up and running, so not sure if the driver disk
> will do you much good... If you don't mind recompiling, the patch you
> need is this:
>
> --- linux-2.4-xfs/linux/drivers/block/DAC960.c 2001/02/22 21:09:04
> 1.24
> +++ linux-2.4-xfs/linux/drivers/block/DAC960.c 2001/05/03 01:10:53
> 1.25
> @@ -5104,6 +5104,9 @@ static int DAC960_IOCTL(Inode_T *Inode,
> return
> put_user(Controller->GenericDiskInfo.part[MINOR(Inode->i_rdev)]
> .nr_sects,
> (long *) Argument);
> + case BLKBSZSET:
> + /* Set block size. */
> + return blk_ioctl (Inode->i_rdev, Request, Argument);
> case BLKRAGET:
> /* Get Read-Ahead. */
> if ((long *) Argument == NULL) return -EINVAL;
>
> HTH,
>
> -Eric
>
> --
> Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
> sandeen@xxxxxxx SGI, Inc.
|