Skip to contentSkip to conversation

troubles with nohide -- crossmnt

NFS Pascal A. Dupuis 5 participants 7 messages Feb 7, 2008 5 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello,

I'd like to export two filesystems, mounted on one another. The setup is :

some partition mounted as /home/user (parent)
another one as /home/user/archive (child)

The export file contains:
/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

I tried:
-setting the 'nohide' option on the child
-setting the crossmnt on the parent
-permuting the order

Whatever case I try, on the client I ALWAYS see the child directory, and not the parent. Any clue ?

Both systems are linux-2.6.24, debian SID, nfs-kernel-package for the server, nfsv4 compiled as a module.

TIA

Pascal Dupuis

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#2 lore raw
In reply to a message not in the archive
Quoted 11 lines · On Thu, 7 Feb 2008 22:36:05 +0100 "Pascal A. Dupuis"…

Hello,

I'd like to export two filesystems, mounted on one another. The setup is :

some partition mounted as /home/user (parent)
another one as /home/user/archive (child)

The export file contains:
/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

Quoted 32 lines

I tried:

(quoted diff) +0 -3
-setting the 'nohide' option on the child
-setting the crossmnt on the parent
-permuting the order 

Whatever case I try, on the client I ALWAYS see the child directory, and not the parent. Any clue ?

Both systems are linux-2.6.24, debian SID, nfs-kernel-package for the server, nfsv4 compiled as a module.

TIA

Pascal Dupuis

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

-
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 13 lines
Jeff Layton <[email protected]>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs
#4 lore raw
In reply to a message not in the archive
Quoted 8 lines · Jeff Layton
Quoted 3 lines

/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

OK. It made the trick. I didn't notice that both exported FS had the same fsid. Thanks. Maybe this should be included in the FAQS ?

Regards

Pascal Dupuis

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#6 lore raw
In reply to a message not in the archive
Quoted 5 lines · Pascal A. Dupuis
Quoted 3 lines · Jeff Layton
Quoted 3 lines

/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

Quoted 7 lines
Quoted 4 lines

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

OK. It made the trick. I didn't notice that both exported FS had the same fsid. Thanks. Maybe this should be included in the FAQS ?

We are working on changing things so the fsid=0 is not needed...

steved.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#8 lore raw
In reply to a message not in the archive
Quoted 8 lines · Steve Dickson
Quoted 5 lines · Pascal A. Dupuis
Quoted 3 lines · Jeff Layton
Quoted 3 lines

/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

Quoted 8 lines
Quoted 7 lines
Quoted 4 lines

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

OK. It made the trick. I didn't notice that both exported FS had the same fsid. Thanks. Maybe this should be included in the FAQS ?

We are working on changing things so the fsid=0 is not needed...

More helpful than a FAQ entry might just be a warning from exportfs or mountd or whatever--it shouldn't be hard to check for the above.

I've added this to the list at:

http://wiki.linux-nfs.org/wiki/index.php/To_do

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#9 lore raw
Quoted 16 lines · J. Bruce Fields
Quoted 15 lines · Steve Dickson
Quoted 12 lines · Pascal A. Dupuis
Quoted 7 lines · Jeff Layton
Quoted 3 lines

/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

OK. It made the trick. I didn't notice that both exported FS had the same fsid. Thanks. Maybe this should be included in the FAQS ?

Quoted 8 lines
Quoted 1 line

We are working on changing things so the fsid=0 is not needed...

More helpful than a FAQ entry might just be a warning from exportfs or mountd or whatever--it shouldn't be hard to check for the above.

I've added this to the list at:

http://wiki.linux-nfs.org/wiki/index.php/To_do

It might not be a bad idea to also warn if we detect that the user changes the fsid mapping in /etc/exports. If there are active clients at the time of the modification, then that will cause trouble for them.

Cheers
Trond

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs

#11 lore raw
In reply to a message not in the archive
Quoted 23 lines · Trond Myklebust
Quoted 21 lines · J. Bruce Fields
Quoted 8 lines · Steve Dickson
Quoted 5 lines · Pascal A. Dupuis
Quoted 3 lines · Jeff Layton
Quoted 3 lines

/home/user/archive 192.168.1.10(rw,subtree_check,fsid=0)
/home/user 192.168.1.10(rw,subtree_check,fsid=0,crossmnt)

Quoted 8 lines
Quoted 7 lines
Quoted 4 lines

You shouldn't have 2 exports with the same fsid= option. They should be different. I'd suggest giving /home/user fsid=0 and /home/user/archive fsid=1 (or something else).

OK. It made the trick. I didn't notice that both exported FS had the same fsid. Thanks. Maybe this should be included in the FAQS ?

We are working on changing things so the fsid=0 is not needed...

More helpful than a FAQ entry might just be a warning from exportfs or mountd or whatever--it shouldn't be hard to check for the above.

Quoted 7 lines
Quoted 3 lines

I've added this to the list at:

http://wiki.linux-nfs.org/wiki/index.php/To_do

It might not be a bad idea to also warn if we detect that the user changes the fsid mapping in /etc/exports. If there are active clients at the time of the modification, then that will cause trouble for them.

Sure. I've added that too.

(Lots of easy stuff on that list! Help yourselves! OK, probably some dumb or out-of-date stuff there too--may want to ask first.)

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued. Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs