This is one of the greatest annoyances of ZFS. I don't really understand how, a zvol's space can not be accurately enumerated from top to bottom of the tree in 'df' output etc. Why does a "zvol" divorce the space used from the root of the volume?
Gregg Wonderly On Feb 6, 2013, at 5:26 PM, Edward Ned Harvey (opensolarisisdeadlongliveopensolaris) <opensolarisisdeadlongliveopensola...@nedharvey.com> wrote: > I have a bunch of VM's, and some samba shares, etc, on a pool. I created the > VM's using zvol's, specifically so they would have an > appropriaterefreservation and never run out of disk space, even with > snapshots. Today, I ran out of disk space, and all the VM's died. So > obviously it didn't work. > > When I used "zpool status" after the system crashed, I saw this: > NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT > storage 928G 568G 360G - 61% 1.00x ONLINE - > > I did some cleanup, so I could turn things back on ... Freed up about 4G. > > Now, when I use "zpool status" I see this: > NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT > storage 928G 564G 364G - 60% 1.00x ONLINE - > > When I use "zfs list storage" I see this: > NAME USED AVAIL REFER MOUNTPOINT > storage 909G 4.01G 32.5K /storage > > So I guess the lesson is (a) refreservation and zvol alone aren't enough to > ensure your VM's will stay up. and (b) if you want to know how much room is > *actually* available, as in "usable," as in, "how much can I write before I > run out of space," you should use "zfs list" and not "zpoolstatus" > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
