On Thu, 24 Dec 2009 at 04:21, lists@xxxxxxxxxxxxxxx wrote:
I'll try to run a few more nilfs2 tests to find out of it's really an
-ENOSPACE thing.
I was curious enough to just do that right now:
$ cat t-nilfs2.sh
#!/bin/sh
umount /mnt/d1
mkfs.nilfs2 /dev/xvdb
mount -t nilfs2 -o barrier=off /dev/xvdb /mnt/d1
for i in `seq 1 1000`; do
date
dd if=/dev/zero of=/mnt/d1/file.$i bs=1M count=100 2>/dev/null
sync && rm -v /mnt/d1/file.$i && sync
ls -la /mnt/d1
df -k /mnt/d1 | grep -v Files
echo
done
--------------
So, basically I'm just writing 100MB to nilfs, then deleting the file
again, sync and making sure that file.$i has been indeed deleted. Here's
just the output from the df(1) commands:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvdb 2088956 114684 1867776 6% /mnt/d1
/dev/xvdb 2088956 221180 1761280 12% /mnt/d1
/dev/xvdb 2088956 327676 1654784 17% /mnt/d1
/dev/xvdb 2088956 434172 1548288 22% /mnt/d1
/dev/xvdb 2088956 524284 1458176 27% /mnt/d1
/dev/xvdb 2088956 638972 1343488 33% /mnt/d1
/dev/xvdb 2088956 745468 1236992 38% /mnt/d1
/dev/xvdb 2088956 835580 1146880 43% /mnt/d1
/dev/xvdb 2088956 958460 1024000 49% /mnt/d1
/dev/xvdb 2088956 1056764 925696 54% /mnt/d1
/dev/xvdb 2088956 1163260 819200 59% /mnt/d1
/dev/xvdb 2088956 1261564 720896 64% /mnt/d1
/dev/xvdb 2088956 1368060 614400 70% /mnt/d1
/dev/xvdb 2088956 1482748 499712 75% /mnt/d1
/dev/xvdb 2088956 1572860 409600 80% /mnt/d1
/dev/xvdb 2088956 1687548 294912 86% /mnt/d1
/dev/xvdb 2088956 1794044 188416 91% /mnt/d1
/dev/xvdb 2088956 1892348 90112 96% /mnt/d1
/dev/xvdb 2088956 1957884 24576 99% /mnt/d1
/dev/xvdb 2088956 1974268 8192 100% /mnt/d1
/dev/xvdb 2088956 1974268 8192 100% /mnt/d1
/dev/xvdb 2088956 1974268 8192 100% /mnt/d1
[...]
With 8K free, dd(1) was unable to write any data to the filesystem. This
is all with Linux 2.6.32 (x86-64) and nilfs2-tools 2.0.14-5, but I think
this happened with earlier kernels too. Again, perhaps nilfs2 is
supposed to work that way, somewhere the "old" versions of the
filesystem have to be stored and this the fs fills up of course - but
you tell me :-)
Christian.
--
make bzImage, not war
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
