hi,
On Mon, Jan 28, 2002 at 12:02:59PM -0500, Dave Sill wrote:
> I've got a terabyte RAID that I'm trying to set up as a single XFS
> filesystem. mkfs fails with:
>
> [root@malachite root]# mkfs.xfs -f /dev/sdb1
> meta-data=/dev/sdb1 isize=256 agcount=224, agsize=1048576 blks
> data = bsize=4096 blocks=234870292, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=0
> = imaxbits=32
> naming =version 2 bsize=4096
> log =internal log bsize=4096 blocks=28670
> realtime =none extsz=65536 blocks=0, rtextents=0
> mkfs.xfs: read failed: Input/output error
> mkfs.xfs: data size check failed
> mkfs.xfs: mount initialization failed
> [root@malachite root]#
Basically, what happens here is mkfs.xfs asks the device how
big it is (using the BLKGETSIZE ioctl) and before starting to
write to the disk, mkfs seeks to 4K from the end of the device
and issues a read (to validate the size which the device driver
gave it).
It looks like for your terabyte RAID, this read is failing (the
driver is giving EIO), hence the message "data size check failed".
mkfs.xfs will refuse to run on a device which exhibits this anti-
social behavior.
> I had no problems mkfs'ing it as e2fs, e3fs, and reiserfs.
These programs are not doing this lseek/read check to validate
the size of the device.
> I'm running under the 1.02a installer on an Athlon:
>
> [root@malachite root]# uname -a
> Linux malachite 2.4.9-13SGI_XFS_1.0.2 #1 Thu Nov 15 14:28:44 CST 2001 i686
> unknown
> [root@malachite root]#
>
> I installed the xfs programs from the RPM:
>
> xfsprogs-1.3.13-0.i386.rpm
>
> Any ideas?
>
Your terabyte RAID device driver seems to have a bug in either
the code which reports its size, or in reading near the end of
the device.
Hope this helps.
cheers.
--
Nathan
|