xfs
[Top] [All Lists]

Re: mkfs.xfs says "can't determine device size"

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: mkfs.xfs says "can't determine device size"
From: Steve Lord <lord@xxxxxxx>
Date: 28 Feb 2002 15:22:18 -0600
Cc: Alvaro Figueroa <fede2@xxxxxxxxxxxxxxxxxxxxx>, XFS to linux port mailing list <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20020301081649.T193798@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <1014920792.17527.12.camel@lucy> <20020301081649.T193798@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Thu, 2002-02-28 at 15:16, Nathan Scott wrote:
> On Thu, Feb 28, 2002 at 12:26:32PM -0600, Alvaro Figueroa wrote:
> > mkfs -t xfs -f /dev/scsi/host1/bus0/target8/lun0/part1 
> > 
> > mkfs.xfs: warning - cannot set blocksize on block device
> > /dev/scsi/host1/bus0/target8/lun0/part1: Invalid argument
> > ...
> > Any ideas?
> > 
> 
> The device driver you're using doesn't support the BLKBSZSET ioctl.
> It should also be returning ENOTTY (rather than EINVAL) according
> to a recent discussion on linux-kernel for ioctl commands which it
> doesn't recognise.
> 
> [ Is there a FAQ entry for this one, Seth? ]
> 
> > mkfs.xfs: can't determine device size
> 
> I assume you're using mkfs from xfsprogs-2.0.0 -- in which case,
> your device driver also doesn't support the BLKGETSIZE64 ioctl.
> 
> This second one is fatal because mkfs needs to know how big your
> device is.  You should be able to make some more progress using
> a filesystem in a regular file - from a quick look in the code,
> that short-circuits out before issuing the ioctl.  Otherwise, you
> will need to contact the author for your device driver I think,
> and see if they have fixed this.

Does a mkfs with a -d size=xxxxb still do the ioctl call? Probably
since it is in the initialization code isn't it.

Steve


-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


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