Don't take this as gospel, and someone chime in if I'm off here, but I
just saw an ARC case about this issue....
The fw in the T3 line might already take the NV_SYNC request. If it
doesn't then we'll have a conf file where you can set it per array.
Also, I would think the module or conf file would come with Sun arrays
already listed.
Andy Lubel wrote:
yeah i saw that post about the other arrays but none for this EOL'd hunk of
metal. i have some 6130's but hopefully by the time they are implemented we
will have retired this nfs stuff and stepped into zvol iscsi targets.
thanks anyways.. back to the drawing board on how to resolve this!
-Andy
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Torrey McMahon
Sent: Fri 4/20/2007 6:00 PM
To: Marion Hakanson
Cc: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] ZFS+NFS on storedge 6120 (sun t4)
Marion Hakanson wrote:
[EMAIL PROTECTED] said:
We have been combing the message boards and it looks like there was a lot of
talk about this interaction of zfs+nfs back in november and before but since
i have not seen much. It seems the only fix up to that date was to disable
zil, is that still the case? Did anyone ever get closure on this?
There's a way to tell your 6120 to ignore ZFS cache flushes, until ZFS
learns to do that itself. See:
http://mail.opensolaris.org/pipermail/zfs-discuss/2006-December/024194.html
The 6120 isn't the same as a 6130/61340/6540. The instructions
referenced above won't work on a T3/T3+/6120/6320
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
