NFS shares inaccessible after upgrade from 7.2.0 to 8.0.0 due to default security type

195 views
Skip to first unread message

dchubarov

unread,
Jun 3, 2017, 3:43:43 AM6/3/17
to Isilon Technical User Group
When recently upgrading OneFS from 7.2.0.2 to 8.0.0.4 with remote assistance from a certified engineer we ran into an issue which does not seem to be described in the Isilon Knowledge Base, so I thought perhaps posting it could help someone out there.

NFS exports that do not have custom security types selected become inaccessible after the upgrade in a peculiar way.

NFS mount command on the client times out yet showmount isilon_node_ip shows the client ip listed.

Fortunately we had an export with a custom security type that was not affected, which helped to narrow the problem down.

It appears that the problem gets resolved when selecting a custom UNIX security type using either the OneFS web administration interface or issuing the CLI command for each affected export
isi nfs export modify export_id --security-flavors unix 

Sergey Kamenetskiy

unread,
Jun 4, 2017, 12:46:43 AM6/4/17
to isilon-u...@googlegroups.com
Did DellEMC support have anything to say about that ?  I am about to upgrade to 8.0.0.4 myself

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

dchubarov

unread,
Jun 4, 2017, 5:24:29 AM6/4/17
to Isilon Technical User Group
So far from our support engineer we got a rather vague suggestion that "Security did change a lot in version 8.0.0" and an advice to look at Access Zones settings. Neither was particularly helpful.
Also we requested and received a copy of Article 480190, "After upgrading to OneFS 8.0.0.0, SMB shares and NFS exports are no longer available" that is accessible only to EMC partners who have a DELL/EMC salesforge account and not accessible through Powerlink. However this note did not apply in our case. If you are intereseted I can forward it to you in private.

We receive third-party support from DELL/EMC distribution partner. If there will be more information from our support engineer that I could post here I will reply to this thread.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.

Josh

unread,
Jun 5, 2017, 1:05:56 PM6/5/17
to Isilon Technical User Group
This will be very interesting for me as well.  We're scheduled to upgrade 2 clusters to 8.0.0.4 from 7.2.x this weekend...

Chris Stacey

unread,
Jun 8, 2017, 4:45:30 PM6/8/17
to Isilon Technical User Group
Hi dchubarov,

Support should have pointed you at https://support.emc.com/kb/496341 which is supposed to be accessible to everyone and sounds like the issue you hit.

Cheers,
Chris

Dmitri Chubarov

unread,
Jun 8, 2017, 9:31:44 PM6/8/17
to isilon-u...@googlegroups.com
Chris, thank you. That is exactly the problem we ran into. Wish we knew that before.


--
You received this message because you are subscribed to a topic in the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/isilon-user-group/Ho5B-7CrY6w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to isilon-user-group+unsubscribe@googlegroups.com.

Josh

unread,
Jun 11, 2017, 2:17:13 PM6/11/17
to Isilon Technical User Group
Thanks Chris,

This post just saved me during my upgrade this weekend.  We hit a similar issue, no NFS mounts were working for clients.  Ended up being this exact issue, no security type applied to any exports post upgrade.  What's annoying is that the other cluster I upgraded worked just fine.

You are a scholar and a gentleman!

Steve Bogdanski

unread,
Oct 3, 2017, 4:22:47 PM10/3/17
to Isilon Technical User Group
I remember EMC support mentioning this known bug to me AFTER I had completed the upgrade from 7.2.1.4 to 8.0.0.4 last spring.  Luckily it didn't affect either of our clusters, but I was a little alarmed that it hadn't come up in any discussions I had with EMC before the upgrade.
Reply all
Reply to author
Forward
0 new messages