10 messages in org.freebsd.freebsd-fsRe: ZFS resize disk vdev| From | Sent On | Attachments |
|---|---|---|
| Bryan Alves | Dec 8, 2008 9:55 pm | |
| Andrew Snow | Dec 8, 2008 10:40 pm | |
| James R. Van Artsdalen | Dec 9, 2008 12:22 am | |
| Ivan Voras | Dec 9, 2008 1:58 am | |
| Andrew Snow | Dec 9, 2008 4:09 am | |
| Bryan Alves | Dec 9, 2008 8:03 am | |
| Nick Gustas | Dec 9, 2008 8:41 am | |
| Zaphod Beeblebrox | Dec 15, 2008 12:39 pm | |
| Bryan Alves | Dec 15, 2008 1:11 pm | |
| Zaphod Beeblebrox | Dec 15, 2008 2:08 pm |
| Subject: | Re: ZFS resize disk vdev | |
|---|---|---|
| From: | Andrew Snow (and...@modulus.org) | |
| Date: | Dec 8, 2008 10:40:21 pm | |
| List: | org.freebsd.freebsd-fs | |
Bryan Alves wrote:
I'm thinking about using a hardware raid array with ZFS, using a single disk vdev zpool. I want the ability to add/remove disks to an array, and I'm still unsure of the stability of zfs as a whole. I'm looking for an easy way to resize and manage disks that are greater than 2 terabytes. If I have a single block device, /dev/da0, on my system that is represented by a zfs disk vdev, and the size of this block device grows (because the underlying hardware raid expands), will zfs correctly expand? And will it correctly expand in place?
In theory, this works fine - I have never tried it myself. The only other way to expand a zpool is by adding more vdevs: You cannot change a vdev once it is created other than to take it from a single disk to a mirror.
Sun's ZFS best practice guide states that you should avoid a single disk vdev because performance on the whole suffers and is worse than UFS.
I am going to publish some benchmark figures soon to back this up, based on testing I did with a 16 disk hardware RAID6. ZFS was *alot* faster when I gave it the disks in a RAIDZ2 vdev.
- Andrew
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "free...@freebsd.org"