On Tue, 2002-04-23 at 08:16, Stephen Lord wrote:
> We had some ioctl problem reports from mkfs which should now be fixed in
> EVMS 1.0. Someone else reported it was working. I have not tried myself.
I am using EVMS, and see:
root@juniper:~
# mkfs -t xfs /dev/evms/test
mkfs.xfs: warning - cannot set blocksize on block device /dev/evms/test:
Invalid argument
meta-data=/dev/evms/test isize=256 agcount=8, agsize=65536
blks
data = bsize=4096 blocks=524287, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
This is a 2.4.18 kernel (SMP), the evms header says it's version 1.0.0,
and the evms tools are version 1.0.0.
root@juniper:~
# mkfs.xfs -V
mkfs.xfs version 2.0.3
Is that too old a version of mkfs.xfs? It would be a lot easier for me
to see what version of XFS the kernel has built into it if you would
cause the "dmesg" (printk) output at startup to give a version number.
I've given up on finding what version it is after 5 minutes of code
grepping, sorry. Ah... dpkg --status kernel-patch-xfs tells me that
it's version "1.0.2+20020304-2". So do I need a newer one to make XFS
work right with EVMS?
As far as EVMS itself goes, I think it's great. I have experienced
lockups when working with snapshots that I need to explore and document
at some point (if I find some time).
|