On Tue, 2002-01-08 at 18:33, Adam McKenna wrote:
> This is an approx. 270 Gig RAID5 partition on an AMI Megaraid card on
> 2.2.14-xfs (snapshot)..
>
> I get the following error when trying to create the filesystem:
>
> adam@braindb:~$ sudo mkfs.xfs -f /dev/sda9
> mkfs.xfs: warning - cannot set blocksize on block device /dev/sda9: Invalid
> argument
> meta-data=/dev/sda9 isize=256 agcount=65, agsize=1048576 blks
> data = bsize=4096 blocks=67782243, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=0
> naming =version 2 bsize=4096
> log =internal log bsize=4096 blocks=8274
> realtime =none extsz=65536 blocks=0, rtextents=0
> File size limit exceeded
>
> The same thing happens if I try ext2:
>
> adam@braindb:~$ sudo mke2fs /dev/sda9
> mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> 33898496 inodes, 67782243 blocks
> 3389112 blocks (5.00%) reserved for the super user
> First data block=0
> 2069 block groups
> 32768 blocks per group, 32768 fragments per group
> 16384 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
> 2654208,
> 4096000, 7962624, 11239424, 20480000, 23887872
>
> File size limit exceeded
>
> adam@braindb:~$ uname -a
> Linux braindb 2.4.14-xfs #3 SMP Fri Nov 30 01:58:14 PST 2001 i686 unknown
>
> Anyone know what is going on here?
You are being bitten by O_LARGEFILE - the linux kernel now does not let
an application which does not open files with O_LARGEFILE access beyond
2 Gbytes.
Lots of applications seem to rely on glibc doing this for them - so it
may be you need a newer glibc.
Steve
>
> --Adam
>
> --
> Adam McKenna <adam@xxxxxxxxxxxx> | GPG: 17A4 11F7 5E7E C2E7 08AA
> http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|