Just tried with both the current Etch-version and the latest version
available (from Lenny) compiled from source (2.9.8). This is what I get:
2.8.11-1 Etch version with --size=4k (note that you still get the warning):
+(532 /...9.8/mkfs)# mkfs.xfs -f -ssize=4k
/dev/sdc
([EMAIL PROTECTED])
mkfs.xfs: warning - cannot set blocksize on block device /dev/sdc:
Invalid argument
meta-data=/dev/sdc isize=256 agcount=32,
agsize=42865797 blks
= sectsz=4096 attr=0
data = bsize=4096 blocks=1371705504, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks
realtime =none extsz=65536 blocks=0, rtextents=0
2.9.8 Lenny version with --size=4k:
+(531 /...9.8/mkfs)# ./mkfs.xfs -f -ssize=4k
/dev/sdc
ret:1 ([EMAIL PROTECTED])
meta-data=/dev/sdc isize=256 agcount=6,
agsize=268435455 blks
= sectsz=4096 attr=2
data = bsize=4096 blocks=1371705504, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
The Lenny version no longer complains when --size=4k is provided but
mkfs.xfs still can't properly detect it hisself:
+(530 /...9.8/mkfs)# ./mkfs.xfs -f
/dev/sdc
ret:1 ([EMAIL PROTECTED])
mkfs.xfs: warning - cannot set blocksize on block device /dev/sdc:
Invalid argument
Warning: the data subvolume sector size 512 is less than the sector size
reported by the device (4096).
meta-data=/dev/sdc isize=256 agcount=6,
agsize=268435455 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=1371705504, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
existing superblock read failed: Invalid argument
mkfs.xfs: pwrite64 failed: Invalid argument
mkfs.xfs: read failed: Invalid argument
And I guess most people expect mkfs.xfs to properly detect the sector
size (and choose the "ssize") automatically like ie. mkfs.ext3 does, right?
If you need additional info/testing don't hesitate to contact me.
Nathan Scott wrote:
On Sat, 2008-07-05 at 17:48 +0200, Arno van Amersfoort wrote:
Package: xfsprogs
Version: 2.8.11-1
Platform: 32bit x86
You should be able to use -ssize=4k on the mkfs command line to work
around this. In more recent versions of xfsprogs, mkfs.xfs does a
better job of handling this automatically... could you try the most
recent version 2.9.5 or so, and let me know if it works for you? I
don't have access to such hardware, so can't really confirm.
thanks.
--
Nathan
--
Ing. A.C.J. van Amersfoort (Arno)
Electronics & ICT Engineer
----------------------------------------------------------------
Leiden Institute of Physics (LION), Electronics Department (ELD)
Huygens Laboratory (Room 1007), Leiden University
Postal Address: P.O. Box 9504, 2300 RA Leiden
Visit Address : Niels Bohrweg 2, 2333 CA Leiden
The Netherlands
----------------------------------------------------------------
Phone : +31-(0)71-527.1894
Fax : +31-(0)71-527.5819
E-mail : [EMAIL PROTECTED]
Homepage : http://rocky.eld.leidenuniv.nl
