It seems to be common practice to delete the default exports (NFS, SMB) for /ifs

and create more specific exports, at least for any serious use other

than demo or testing,

(If you use InsightIQ, make sure it can NFS-mount /ifs/.ifsvar/modules/fsa)

Cheers

-- Peter

Thank you for your prompt answer! We are not using InsightIQ. However in one of the NFS exports vmware is running. Can I safely remove the /ifs NFS export not interrupting any operations?

Best,

Marek

See what you mean.. can you test it as follows?

create and export (allow sub-mounts) /ifs/test

create  /ifs/test/sub and mount it from client, run a VM on it

export /ifs/test/sub

delete export for /ifs/test

check mounted /ifs/test/sub on client/VM

-- P.

Gentlemen, while you're correct that deleting an export (the default /ifs) won't affect a lower-level export. It's important to understand that most client OSes if told to mount /ifs/data, and they find an export at /ifs, they will mount /ifs, and then the subdirectory data.  So if you remove the export from the cluster you might see stale mounts, I have seen this in the field.  It has nothing to do with Isilon and is specific to the ClientOS's NFS client.

~Chris Klosterman

Senior SA, EMC Isilon Offer & Enablement Team

chris.klosterman@emc.com

twitter: @croaking

Chris,

what if /ifs export is set to not allow mounting of subdirectories ?

Then it shouldn't matter. However, the /ifs export, by default, does have mounting sub directories enabled