That's a good idea, thanks. I get the feeling the remainder won't be zero,
which will back up the misalignment theory. After a bit more digging, it seems
the problem is just an NTFS issue and can be addressed irrespective of
underlying storage system.
I think I'm going to try the process in the
On Thu, Mar 18, 2010 at 14:44, Chris Murray wrote:
> Good evening,
> I understand that NTFS & VMDK do not relate to Solaris or ZFS, but I was
> wondering if anyone has any experience of checking the alignment of data
> blocks through that stack?
It seems to me there's a simple way to check. Pic
I have only heard of alignment being discussed in reference to
block-based storage (like DASD/iSCSI/FC). I'm not really sure how it
would work out over NFS. I do see why you are asking though.
My understanding is that VMDK files are basically 'aligned' but the
partitions inside of them may not
On Thu, Mar 18, 2010 at 2:44 PM, Chris Murray wrote:
> Good evening,
> I understand that NTFS & VMDK do not relate to Solaris or ZFS, but I was
> wondering if anyone has any experience of checking the alignment of data
> blocks through that stack?
>
NetApp has a great little tool called mbrscan/m
Not having specific knowledge of the VMDK format, I think what you are
seeing is that there is extra data associated with maintaining the VMDK.
If you are seeing lower dedup ratios than you would expect, it sounds
like some of this extra data could be added to each block.
The VMDK spec appears
Sent: 18 March 2010 18:45
To: zfs-discuss@opensolaris.org
Subject: [zfs-discuss] Validating alignment of NTFS/VMDK/ZFS blocks
Good evening,
I understand that NTFS & VMDK do not relate to Solaris or ZFS, but I was
wondering if anyone has any experience of checking the alignment of data
block
Good evening,
I understand that NTFS & VMDK do not relate to Solaris or ZFS, but I was
wondering if anyone has any experience of checking the alignment of data blocks
through that stack?
I have a VMware ESX 4.0 host using storage presented over NFS from ZFS
filesystems (recordsize 4KB). Within
