On Thu, March 10, 2011 13:04, wessels wrote:
> 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
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 n
On Thu, Mar 10, 2011 at 9:45 AM, Richard Elling
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. So you will need to
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.
On Thu, Mar 10, 2011 at 12:15 AM, Matthew Anderson
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 helps the issue.
> At the mome
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 disab