Hi Dave -
Can you run this through strace, to see where things go wrong? All
mkfs.xfs is doing when it failes, is trying to read the last block on the
device.
Since I don't have 1T laying around, I tried it on a file:
[root@lite sda2]# mkfs.xfs -d file,name=new-filesystem,size=234870292b
meta-data=new-filesystem isize=256 agcount=224, agsize=1048576
blks
data = bsize=4096 blocks=234870292, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=28670
realtime =none extsz=65536 blocks=0, rtextents=0
it also works via the loop device (so mkfs.xfs thinks it's talking to a
real device):
[root@lite sda2]# losetup /dev/loop0 new-filesystem
[root@lite sda2]# mkfs.xfs -f /dev/loop0
Invalid argument
meta-data=/dev/loop0 isize=256 agcount=224, agsize=1048576
blks
data = bsize=4096 blocks=234870292, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=28670
realtime =none extsz=65536 blocks=0, rtextents=0
-Eric
On 28 Jan 2002, Dave Sill wrote:
> Thought so. Unfortunately, I'm still seeing the same problem after
> installing xfsprogs-1.3.17:
|