Re: [zfs-discuss] (Practical) limit on the number of snapshots?
By having a snapshot you are not releasing the space forcing zfs to allocate new space from other parts of a disk drive. This may lead (depending on workload) to more fragmentation, less localized data (more and longer seeks). ZFS uses COW (copy on write) during writes. This means that it first has to find a new location for the data and when this data is written, the original block is released. When using snapshots, the original block is not released. I don't think the use of snapshots will alter the way data is fragmented or localized on disk. --- PeterVG -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] ZFS concat pool
I have a need to created pool that only concatenates the LUNS assigned to it. The default for a pool is stripe and other possibilities are mirror, raidz and raidz2. Is there any way I can create concat pools. Main reason is that the underlying LUNs are already striping and we do not want to stripe in ZFS *and* in the storage cabinet (internal politics). To my knowledge the only other possibility (if ZFS can't do it) is using SVM. Greetings, Peter -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] Re: ZFS Inexpensive SATA Whitebox
Hi There, You might want to check the HCL at http://www.sun.com/bigadmin/hcl to find out which hardware is supported by Solaris 10. Greetings, Peter This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
