> Where can I find information on the file allocation methodology used by ZFS?
You've inspired me to blog again:
http://blogs.sun.com/bonwick/entry/zfs_block_allocation
I'll describe the way we manage free space in the next post.
Jeff
___
zfs
Hello Robert,
Thursday, November 2, 2006, 5:12:37 PM, you wrote:
RM> Hello zfs-discuss,
RM> Server: x4500, 2x Opetron 285 (dual-core), 16GB RAM, 48x500GB
RM> filebench/randomread script, filesize=256GB
RM> 2 disks for system, 2 disks as hot-spares, atime set to off for a
RM> pool, cache_bshif
Where can I find information on the file allocation methodology used by ZFS?
Does it use Indexed Allocation?
What strategy does it use to manage the free space on disk? Bit vector,
linked list or something new?
Thanks!
Bret
This message posted from opensolaris.org
6140: 2 x 2GB cache controllers - 4Gbit FC, 16 x 4Gbit 146GB FC 15K spindlesUnfortunately I don't have a 4Gbit HBA or multiple 2Gbit cards, since the above 6140 must be one of the fastest "building" blocks available. I would have loved to see (using multiple HBA's) how much IO's one could get from
> zpool status
> # uncomment the following lines if you want to see
> the system think
> # it can still read and write to the filesystem after
> the backing store has gone.
Hi
UNIX unlink() syscall doesn't remove the inode if its in use. Its marked to be
unliked when its use count falls to zero.
