You mention downloading the beta and the cvs tree, are you running commands
from the beta with the kernel from the cvs tree?
There will be problems if you are doing this, although your mkfs output
does not go with that. Can you check the /dev entry for hdb2, it should look
like this:
brw-rw---- 1 root disk 3, 66 Aug 24 2000 /dev/hdb2
Also, if you do need to rebuild user space commands from the cvs tree
it is fairly easy. First you need to install the e2fsprogs-devel code,
this is fairly easy to locate on the net if you do not have it (go
to freshmeat and do a search).
cd into the cmd/xfsprogs directory and type
./Makepkgs
this will build the rpm files for the commands, you can just do an rpm -U
with these packages. Even though the name has changed from the beta it
will still update on top of the beta rpms.
Steve
>> hello,
>> i've downloaded the linux-2.4-xfs and the linux-2.4-xfs-beta from the cvs
>> some day's ago.
>> i've got them compiled with gcc-2.95.2 but when i try to create a filesystem
>> on partitions larger than 2 gig, i get the following:
>> belana:~ # mkfs.xfs /dev/hdb2
>> /dev/hdb2: Invalid argument
>> can't get size of data subvolume
>> Usage: mkfs.xfs
>> /* blocksize */ [-b log=n|size=num]
>> /* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num,
>> sunit=value,swidth=value,unwritten=0|1]
>> /* inode size */ [-i log=n|perblock=n|size=num,maxpct=n]
>> /* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx]
>> /* naming */ [-n log=n|size=num|version=n]
>> /* prototype file */ [-p fname]
>> /* quiet */ [-q]
>> /* version */ [-V]
>> /* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx]
>> devicename
>> devicename is required unless -d name=xxx is given
>> internal 1000 block log is default unless overridden or using a
>> volumemanager with log
>> num is xxx (bytes), or xxxb (blocks), or xxxk (xxx KB), or xxxm (xxx MB)
>> value is xxx (512 blocks)
>> for the entire device (/dev/hdb) it works.
>> with gcc-2.91.66 (egcs 1.12) i can't compile the kernel at all.
>> any suggestions?
|