Re: [zfs-discuss] BugID formally known as 6746456

2009-06-26 Thread Rob Healey
This appears to be the fix related to the ACL's which they seem to throw all of 
the ASSERT panics in zfs_fuid.c under even if they have nothing to do with 
ACL's; my case being one of those.

Thanks for the pointer though!

-Rob
-- 
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


[zfs-discuss] BugID formally known as 6746456

2009-06-24 Thread Rob Healey
Does anyone know if related problems to the panic's dismissed as duplicate of 
6746456 ever resulted in Solaris 10 patches? It sounds like they were actually 
solved in OpenSolaris but S10 is still panicing predictably when Linux NFS 
clients try to change a nobody UID/GID on a ZFS exported filesystem.

Specifically the NFS induced panics related to the nobody id not mapping 
correctly, or, more precisely, attempts to change user/group ID nobody causing 
S10u7 to blow chunks in zfs_fuid.c zfs_fuid_table_load's ASSERT?

While the workaround to change the id's on the server is possible, it pretty 
much torpedo's management's view of Solaris' stability and sending fileserver 
duty back to Linux... :( Anybody could create a nobody file and put the system 
into endless boot-loops without this being patched.

I'm hoping further work on this issue was done on the S10 side of the house and 
there is a stealthy patch ID that can fix the issue.

Thanks,

-Rob
-- 
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss