From: sct@dcs.ed.ac.uk (Stephen Tweedie) Subject: Re: Kernel crash: Need help fixing my Ext2fs Date: 15 Apr 1993 00:17:16 GMT
In article <1qgvvsINNrb4@serv-200.dfki.uni-kl.de>, malik@dfki.uni-kl.de (Thomas Malik) writes:
> When i now changed to ext2 fs, mke2fs didn't correctly allocate my
> 32 MB root partition. While there had been ~8MB left on that fs
> (output from df and e2fsck), write accesses had 'no space left on
> device' as result.
There is a possible cause for this which has tripped up other users
before now.
The recent ext2fs now respects the FSIZE resource limit, as set by the
"ulimit" command in bash. Type "ulimit -a" to see your current
limits. If you have a filesize ulimit in place, then you can get "no
space left" errors even if there is space left on the device.
The next release of ext2fs will report "filesize limit exceeded" in
this situation rather than "no space left".
> Beside that, i did get these 'bad directory entry errors' from time
> to time.
This was a known bug in e2fsprogs-0.2c. Upgrade to version 0.2d.
Cheers,
Stephen Tweedie.