>The reason that I want to use up the inode is we need to test the >behaviors in the case of both block and inode are used up. If only fill >up the block, creating an empty file still succeeds.
Pretty much the only way to tell if you've used up all the space available for file nodes is to actually try creating a file, though if 'df -e' returns 0 you *may* not be able to create any new files. It may be possible to create empty files (and very small ones) even if there are no free blocks (empty files don't require data blocks, small files can be packed into the inode). To generate a full file system most efficiently, presuming you don't actually need a particular mix of files, I'd suggest writing a single large file in large blocks (1 megabyte or more) until you get ENOSPC; then writing a smaller file in small blocks (512 bytes) until ENOSPC; then trying a smaller file once more; and then creating empty files until you run out of inodes. This should work pretty well on UFS, ZFS, and QFS, even though the three have quite different storage structures. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
