| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: mkfs.xfs says "can't determine device size" |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 1 Mar 2002 08:26:21 +1100 |
| Cc: | Alvaro Figueroa <fede2@xxxxxxxxxxxxxxxxxxxxx>, XFS to linux port mailing list <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1014931338.24566.137.camel@xxxxxxxxxxxxxxxxxxxx>; from lord@xxxxxxx on Thu, Feb 28, 2002 at 03:22:18PM -0600 |
| References: | <1014920792.17527.12.camel@lucy> <20020301081649.T193798@xxxxxxxxxxxxxxxxxxxxxxxx> <1014931338.24566.137.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Thu, Feb 28, 2002 at 03:22:18PM -0600, Steve Lord wrote: > On Thu, 2002-02-28 at 15:16, Nathan Scott wrote: > > 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. yes, looks like it does still do the ioctl in that case. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: mkfs.xfs says "can't determine device size", Steve Lord |
|---|---|
| Next by Date: | Re: mkfs.xfs says "can't determine device size", Eric Sandeen |
| Previous by Thread: | Re: mkfs.xfs says "can't determine device size", Steve Lord |
| Next by Thread: | Re: mkfs.xfs says "can't determine device size", Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |