Hello, Any comments/suggestions about this would be very nice..
Thanks! -- Pasi On Fri, Feb 08, 2013 at 05:09:56PM +0200, Pasi Kärkkäinen wrote: > > I'm seeing weird output aswell: > > # zpool list foo > NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT > foo 5.44T 4.44T 1023G 81% 14.49x ONLINE - > > # zfs list | grep foo > foo 62.9T 0 250G /volumes/foo > foo/.nza-reserve 31K 100M 31K none > foo/foo 62.6T 0 62.6T /volumes/foo/foo > > # zfs list -o space foo > NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD > foo 0 62.9T 0 250G 0 62.7T > > # zfs list -o space foo/foo > NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD > foo/foo 0 62.6T 0 62.6T 0 0 > > > What's the correct way of finding out what actually uses/reserves that 1023G > of FREE in the zpool? > > At this point the filesystems are full, and it's not possible to write to > them anymore. > Also creating new filesystems to the pool fail: > > "Operation completed with error: cannot create 'foo/Test': out of space" > > So the zpool is full for real. > > I'd like to better understand what actually uses that 1023G of FREE space > reported by zpool.. > 1023G out of 4.32T is around 22% overhead.. > zpool "foo" consists of 3x mirror vdevs, so there's no raidz involved. > > 62.6T / 14.49x dedup-ratio = 4.32T > Which is pretty close to the ALLOC value reported by zpool.. > > Data on the filesystem is VM images written over NFS. > > > Thanks, > > -- Pasi > > _______________________________________________ zfs-discuss mailing list firstname.lastname@example.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss