But even the 'zfs list -o space' is now limited by not displaying snapshots
by default, so the catch all is now
zfs list -o space -t all
shouldn't miss anything then …
;-)
Craig
On 10 Mar 2011, at 03:38, Richard Elling wrote:
On Mar 9, 2011, at 4:05 PM, Tom Fanning wrote:
On
Hi All,
I've run into a problem with my OpenSolaris system and NTFS, I can't seem to
make sense of it.
The server running the virtual machines is Ubuntu Server 10.04 running KVM.
Storage is presented via NFS over Infiniband. ZFS is not running compression or
dedup. Zil is also currently
On Thu, Mar 10, 2011 at 12:15 AM, Matthew Anderson
matth...@ihostsolutions.com.au wrote:
I have a feeling it's to do with ZFS's recordsize property but haven't been
able to find any solid testing done with NTFS. I'm going to do some testing
using smaller record sizes tonight to see if that
On Mar 10, 2011, at 12:15 AM, Matthew Anderson wrote:
Hi All,
I've run into a problem with my OpenSolaris system and NTFS, I can't seem to
make sense of it.
The server running the virtual machines is Ubuntu Server 10.04 running KVM.
Storage is presented via NFS over Infiniband. ZFS
On Thu, Mar 10, 2011 at 9:45 AM, Richard Elling
richard.ell...@gmail.com wrote:
Default recordsize for NFS is 128K. For the VM case, you will want to match
the block size of
the clients. However, once the file (on the NFS server) is created with 128K
records, it will remain
at 128K forever.
And make sure you align your NTFS partition regardless off the
underlying storage. Windows 2003 and before DONT do this by default, 7
and 2008 choose a default offset off 1Mb. But better check it in
advance with diskpart. Lastly format your NTFS filesystem with an
appropriate cluster size. Which
Hello,
I have a Sun 7000 series NAS device, I am trying to back it up via NFS mount on
a Solaris 10 server running Networker 7.6.1. It works but it is extremely
slow, I have tested other mounts and they work much faster. The only
difference (that I can see) between the two mounts are the
