On 3/02/10 01:31 AM, Tonmaus wrote:
Hi James,
am I right to understand that in a nutshell the problem is that if
page 80/83 information is present but corrupt/inaccurate/forged (name
> it as you want), zfs will not get to down to the GUID?
Hi Tonmaus,
If page83 information is present, ZFS will use it. The problem
that Moshe came across is that with the controller he used,
ARC-1680ix, the target/lun assignment algorithm in the firmware
made the disks move around from ZFS' point of view - it appeared
that the firmware was screwing around with the Page83 info and
rather than keeping the info associated with the specific device,
it was ... movinng things around of its own accord.
The GUID is generated from the device id (aka devid) which is
generated from [(1) page83, (2) page80, (3) well-known method of
fabrication] information. You can read more about this in my
presentation about GUIDs and devids:
http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf
cheers,
James
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
