Skip to contentSkip to conversation

NFS changement between 2.6.9 and 2.6.10?

DISCUSSION Damien "Zaide 2 participants 3 messages Jan 26, 2005

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

hi,
I have a nfsV3 server running linux 2.6.9, all is good when I "ls -alR" my nfs exported directory on my client after I chroot() in this directory and ls -alR too that well. But when i update my server to linux 2.6.10 and "ls -alR" my nfs directory is allways good but when I chroot() inside, my chroot command is locked and I can't ls my nfs directory. I have launch a sniffer and the packet seams to be send.
Do you have any informations about this? a changement beetwen 2.6.9 and 2.6.10? a patch? a bug?

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#1 lore raw

on den 26.01.2005 Klokka 11:44 (+0100) skreiv Damien "Zaide":

Quoted 10 lines

hi,
I have a nfsV3 server running linux 2.6.9, all is good when I "ls -alR" my nfs exported directory on my client after I chroot() in this directory and ls -alR too that well.
But when i update my server to linux 2.6.10 and "ls -alR" my nfs directory is allways good but when I chroot() inside, my chroot command is locked and I can't ls my nfs directory.
I have launch a sniffer and the packet seams to be send.
Do you have any informations about this? a changement beetwen 2.6.9 and 2.6.10? a patch? a bug?

I don't see how an NFS change could do this. The VFS is the part of the kernel that handles the actual details of chroot. NFS neither knows nor cares.

Cheers,
Trond

Signature · 12 lines
Trond Myklebust <[email protected]>



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
#2 lore raw

on den 26.01.2005 Klokka 11:43 (-0800) skreiv Trond Myklebust:

Quoted 12 lines

on den 26.01.2005 Klokka 11:44 (+0100) skreiv Damien "Zaide":

Quoted 10 lines

hi,
I have a nfsV3 server running linux 2.6.9, all is good when I "ls -alR" my nfs exported directory on my client after I chroot() in this directory and ls -alR too that well.
But when i update my server to linux 2.6.10 and "ls -alR" my nfs directory is allways good but when I chroot() inside, my chroot command is locked and I can't ls my nfs directory.
I have launch a sniffer and the packet seams to be send.
Do you have any informations about this? a changement beetwen 2.6.9 and 2.6.10? a patch? a bug?

Quoted 3 lines

I don't see how an NFS change could do this. The VFS is the part of the kernel that handles the actual details of chroot. NFS neither knows nor cares.

The other thing is that there were no NFS client changes that went in between 2.6.9 and 2.6.10. 8-)

Cheers,
Trond

Signature · 12 lines
Trond Myklebust <[email protected]>



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs