abis baca artikel zfs dari sun http://www.sun.com/2004-0914/feature/
keren juga nih. > With traditional volumes, storage is fragmented and stranded. With ZFS' > common storage pool, > there are no partitions to manage berakhirnya jaman perbedaan partisi dan filesystem ? atau kalau cuma menyederhanakan tools , di linux bisa saja dibikin tool gabungan parted dan LVM >All operations are also copy-on-write. Live data is never overwritten. ZFS >writes data to a new block >before changing the data pointers and committing >the write. Copy-on-write provides several benefits: > > * Always-valid on-disk state > * Consistent, reliable backups > * Data rollback to known point in time data rollback to known point in time ? sepertinya bakal makan space banyak sekali ya ? > ZFS can self-heal data in a mirrored or RAID configuration. When one copy is > damaged, ZFS > detects it via the checksum and uses another copy to repair it. > "The cost of doing something like a checksum is no longer prohibitive. > Burning a small percentage > of the CPU to know that data is intact is a > price that administrators would gladly pay," says Moore. > To efficiently use all of this capacity, file systems grow and shrink > automatically as users add or > remove data. Administrators can set quotas to limit space consumption and > reservations to > guarantee future availability of space. ZFS also provides compression to > reduce disk space and I/O > bandwidth requirements. checksum, compression, processing costnya tinggi sekali sepertinya ideal untuk separated storage, SAN/NAS. imo nggak cocok buat all in one server. > Nah di zfs udah gak usah pusing soal inodes dan volumes lagi, karena > nggak perlu ada. > Multiple block sizes, automatically chosen to match workload btw yang ini cari dimana ya ? - ak
