Re: nfs problems
On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares ==from lathe.coyote.den / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) Gene, Add no_root_squash here, and root will be able to write on the clients. That _is_ what you want, isn't it? Petter -- I'm ionized Are you sure? I'm positive. pgpsc_bIZWLtb.pgp Description: OpenPGP digital signature
Re: nfs problems
On Fri, 8 May 2015 06:51:43 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 02:55:53 Petter Adsen wrote: That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. If you want to read/write file as your normal user, just make sure that the UID is the same on both systems. You might want to edit /etc/passwd on one of the boxes for that, and then you can use find to chown any files that are owned by the old UID. You shouldn't need to do anything other than that. There are other ways to do this, but that is the way I do it at home so I don't need to mess with UID mapping. Or _is_ the UID on both client and server already identical? Petter -- I'm ionized Are you sure? I'm positive. pgpp8XwvX2fot.pgp Description: OpenPGP digital signature
Re: nfs problems
On Friday 08 May 2015 02:55:53 Petter Adsen wrote: On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares ==from lathe.coyote.den / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) Gene, Add no_root_squash here, and root will be able to write on the clients. That might be handy, but 99% of what I would need to do would be done by the user, me. Something like finding some interesting code on the net, downloading it here then moving it to one of those machines, going from say coyote:/home/gene/Downloads, to lathe:/home/gene/linuxcnc/nc_files to put it in the normal data directory for linuxcnc. All as me, gene. If, for instance I dl a firmware zip, the unpacked version of which goes into lathe:/lib/firmware/hm2, I'd copy it to my home tree there, then goto that machine in person or with an ssh -Y session, and use a sudo mc session to unpack move the firmware modules. In that event, I'd be just as well to change the / above to /home/gene. So that part isn't exactly painted on the barn for posterity. And since I'd like to be able to reverse the procedure, an /etc/init.d script that restarts the shebang in one swell foop would be handier than bottled beer. One of these machines has an nfs-common script that does idmapd and statd, and another for the nfs-kernel-server, and I don't see any real reason I can't merge them both into a single /etc/init.d/nfs command so that if I change something in the exports or fstab, all the refreshing to see the effect of the change is done with one command on each of the two machines effected. A full, 2 way share that works from all machines is the target. Limiting the share to /home/gene, isn't that much of a hardship. That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. Thanks Petter Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505080651.43856.ghesk...@wdtv.com
Re: nfs problems
* Petter Adsen pet...@synth.no [2015-05-08 13:03 +0200]: On Fri, 8 May 2015 06:51:43 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 02:55:53 Petter Adsen wrote: That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. If you want to read/write file as your normal user, just make sure that the UID is the same on both systems. You might want to edit /etc/passwd Or even run nis within your LAN... Elimar -- Do you smell something burning or is it me? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508132454.ga...@baumbart.home.lxtec.de
Re: nfs problems
Hi, On 05/08/2015 09:00 AM, Petter Adsen wrote: On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: i just finished wrestling with NFS set-up problems myself. Add no_root_squash here, and root will be able to write on the clients. But isn't there a potential security risk in using that option? AFAIK, with that option enabled, a remote root user (on the nfs client) could gain root privileges the nfs server. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/miis8s$15h$1...@news.albasani.net
Re: nfs problems
On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares /etc/fstab - or at least the mount command from the machine trying to use the shares. Brian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150507213651.2e13b...@cedar.deldotd.com
Re: nfs problems
On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares ==from lathe.coyote.den / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) == /etc/fstab - or at least the mount command from the machine trying to use the shares. == # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass # / was on /dev/sda1 during installation UUID=9fe9e68d-9827-4c8b-af4a-0753996f5e04 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=e03b6db9-47ff-4c59-9956-b5f69e3c5957 noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 shop.coyote.den:/ /net/shop nfs4defaults,intr 0 2 lathe.coyote.den:/ /net/lathe nfs4defaults,intr 0 2 lappy.coyote.den:/ /net/lappy nfs4defaults,intr 0 2 UUID=b7657920-d9a2-4379-ae21-08a0651b65cc /amandatapes ext3 defaults0 2 #/home/gene /net/coyote none bind 0 0 === Thanks Brian Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505080050.24695.ghesk...@wdtv.com
Re: nfs problems
On Thu, 23 Apr 2015 23:54:45 -0600 Bob Proulx b...@proulx.com wrote: bri...@aracnet.com wrote: however the client side mount commands are apparently wrong because I get this: mount.nfs4: mounting server:/nfs4exports/home/user1 failed, reason given by server: No such file or directory and as usual the error message is completely unhelpful because /nfs4exports/home/user1 most certainly DOES exist on the server. Hmm... Guessing... What is in /etc/exports? 'exportfs -a'? What does 'showmount -e' show? Bob well that was quite newbie of me to not provide exportfs wasn't it ? i did finally get things working : exportfs /home/user1 192.168.1.1/24(rw,root_squash,insecure,anonuid=501,anongid=501,async,no_subtree_check) and then /etc/fstab server:/home/user1 /mnt/home/user1 nfs4 rw,hard,intr 0 0 and finally sudo mount /mnt/home/user1 now works. I'm sure I had a mismatch between all of the files in terms of path somehow, but i never really did figure out what i did wrong. i'm not sure what the point of using: /home /nfs4exports/home none bind 0 0 as a mount point is. Seems like using that provided some way to simplify the set-up. or maybe it is simplifying the set-up and i just don't realize it. Brian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150424214248.1462d...@cedar.deldotd.com
Re: nfs problems
bri...@aracnet.com wrote: however the client side mount commands are apparently wrong because I get this: mount.nfs4: mounting server:/nfs4exports/home/user1 failed, reason given by server: No such file or directory and as usual the error message is completely unhelpful because /nfs4exports/home/user1 most certainly DOES exist on the server. Hmm... Guessing... What is in /etc/exports? 'exportfs -a'? What does 'showmount -e' show? Bob signature.asc Description: Digital signature
Re: NFS problems with files.
On Mon, Dec 8, 2008 at 6:57 PM, Brian Schrock [EMAIL PROTECTED] wrote: I am testing a courier-postfix setup using nfs for the Maildir folders on debian etch, and my client machine is debian/lenny. Everything seems to work just peachy except for when I use pop/imap for access to the mail. I have tried with both icedove and evolution using imap and pop and the problem seems to be identical. Furthermore I have tried using the Maildir folders on the nfs and on the local server. When I put the Maildir folders on the local machine everything works fine, when I put them on nfs I get the problem. Output of ls -al /var/mail/username/Maildir/new ?- ? ?? ?? 1228445413.V10I5400aaM156972.mail And to get a little weirder when I do... ls -al 1228445413.V10I5400aaM156972.mail On the troubled file and in that directory I get this: ls: 1228445413.V10I5400aaM156972.mail: No such file or directory Hmm. Maybe the inode numbers for the problem files are outside the 32-bit range. If this is the case I can't remember in detail how to solve it - but try forcing both client and server to use version 4 of the NFS protocol. James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFS problems with Mac client
On Tue, Jul 29, 2008 at 06:47:08AM +0200, André Berger wrote: * Alex Samad (2008-07-29): On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote: * Alex Samad (2008-07-28): on the nas box /exports/shared -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared 192.168.8.0/22(rw) Try /exports/shared 192.168.8.0/22(rw,async,no_subtree_check,no_root_squash) and exportfs -rv On the Mac, add to /etc/fstab (assuming your Server is 192.168.8.5): 192.168.8.5:/exports/shared /yourdir nfs locallocks,udp,sync,resvport,bg,intr,rsize=32768,wsize=32768 0 0 still seem to have the same problem, df -h locks up. tried with no lock, ro, removed the rsize and wsize What about tcp instead of udp? tracked down the problem (with the help of another person on the mac interop mailing list), seems like when i stop using --manage-gids, everything is okay, I have some users with more than 16 gids ! -André -- May as well be hung for a sheep as a lamb! Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from http://hvkls.dyndns.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- The lovely woman-child Kaa was mercilessly chained to the cruel post of the warrior-chief Beast, with his barbarian tribe now stacking wood at her nubile feet, when the strong clear voice of the poetic and heroic Handsomas roared, 'Flick your Bic, crisp that chick, and you'll feel my steel through your last meal!' -- Winning sentence, 1984 Bulwer-Lytton bad fiction contest. signature.asc Description: Digital signature
Re: NFS problems with Mac client
* Alex Samad (2008-07-28): on the nas box /exports/shared -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared 192.168.8.0/22(rw) Try /exports/shared 192.168.8.0/22(rw,async,no_subtree_check,no_root_squash) and exportfs -rv On the Mac, add to /etc/fstab (assuming your Server is 192.168.8.5): 192.168.8.5:/exports/shared /yourdir nfs locallocks,udp,sync,resvport,bg,intr,rsize=32768,wsize=32768 0 0 and run automount -v. PS: Locking doesn't work as expected on Leopard. Use nolock or locallocks. -André -- May as well be hung for a sheep as a lamb! Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from http://hvkls.dyndns.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFS problems with Mac client
On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote: * Alex Samad (2008-07-28): on the nas box /exports/shared -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared 192.168.8.0/22(rw) Try /exports/shared 192.168.8.0/22(rw,async,no_subtree_check,no_root_squash) and exportfs -rv On the Mac, add to /etc/fstab (assuming your Server is 192.168.8.5): 192.168.8.5:/exports/shared /yourdir nfs locallocks,udp,sync,resvport,bg,intr,rsize=32768,wsize=32768 0 0 still seem to have the same problem, df -h locks up. tried with no lock, ro, removed the rsize and wsize and run automount -v. PS: Locking doesn't work as expected on Leopard. Use nolock or locallocks. -André -- May as well be hung for a sheep as a lamb! Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from http://hvkls.dyndns.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Uh-oh!! I'm having TOO MUCH FUN!! signature.asc Description: Digital signature
Re: NFS problems with Mac client
* Alex Samad (2008-07-29): On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote: * Alex Samad (2008-07-28): on the nas box /exports/shared -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared 192.168.8.0/22(rw) Try /exports/shared 192.168.8.0/22(rw,async,no_subtree_check,no_root_squash) and exportfs -rv On the Mac, add to /etc/fstab (assuming your Server is 192.168.8.5): 192.168.8.5:/exports/shared /yourdir nfs locallocks,udp,sync,resvport,bg,intr,rsize=32768,wsize=32768 0 0 still seem to have the same problem, df -h locks up. tried with no lock, ro, removed the rsize and wsize What about tcp instead of udp? -André -- May as well be hung for a sheep as a lamb! Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from http://hvkls.dyndns.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFS problems
At 22:02 19/07/2005, you wrote: No, kernel NFS can be either compiled or loaded as a module into a custom kernel. Does anyone know which NFS server I *should* be using? Does anyone know why lockd fails to run? But the userspace daemons (/sbin/rpc.lockd and /sbin/rpc.statd) don't seem to want to start even when I call them from the command line. A quick grep through my kernel config suggests this is because lockd is supposedly built into the kernel; tamora:/usr/src/linux# cat .config | grep -i lockd CONFIG_LOCKD=y CONFIG_LOCKD_V4=y My kernel just shows the first option, and I'm not using the kernel server. Although I can't for the life of me find the option in menuconfig (maybe due to me copying the .config over from my old 2.4 installation...? But I can't find the option in 2.4's menuconfig either). I found it by enabling the Show All Options option while running make xconfig. Using that option I also found that in order to enable CONFIG_LOCKD_V4, I first had to enable NFS server support (NFSD) and then NFSv3. Well, I don't have X on this machine but unchecking the NFS modules does in turn uncheck the lockd module too. If I'm using the userspace server, should I remove the in-kernel NFS server components? Aha, just had another look through menuconfig and found the root of the problem; having NFSD enabled in the kernel stops the userspace server from loading lockd (that'll teach me not to read the help text properly). Just switched back to another kernel and using the kernel server, and both lockd and statd both seem to be running OK, and no more locking errors on the clients. Unfortunately, it still hasn't fixed my other ongoing problem http://lists.debian.org/debian-user/2005/06/msg03111.html with symlinks not working on exported filesystems, but it's a step in the right direction...! Thanks for your help Marty, it set me on the right track! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFS problems
At 18:43 20/07/2005, you wrote: At 22:02 19/07/2005, you wrote: No, kernel NFS can be either compiled or loaded as a module into a custom kernel. Does anyone know which NFS server I *should* be using? Does anyone know why lockd fails to run? But the userspace daemons (/sbin/rpc.lockd and /sbin/rpc.statd) don't seem to want to start even when I call them from the command line. A quick grep through my kernel config suggests this is because lockd is supposedly built into the kernel; tamora:/usr/src/linux# cat .config | grep -i lockd CONFIG_LOCKD=y CONFIG_LOCKD_V4=y My kernel just shows the first option, and I'm not using the kernel server. Although I can't for the life of me find the option in menuconfig (maybe due to me copying the .config over from my old 2.4 installation...? But I can't find the option in 2.4's menuconfig either). I found it by enabling the Show All Options option while running make xconfig. Using that option I also found that in order to enable CONFIG_LOCKD_V4, I first had to enable NFS server support (NFSD) and then NFSv3. Well, I don't have X on this machine but unchecking the NFS modules does in turn uncheck the lockd module too. If I'm using the userspace server, should I remove the in-kernel NFS server components? Aha, just had another look through menuconfig and found the root of the problem; having NFSD enabled in the kernel stops the userspace server from loading lockd (that'll teach me not to read the help text properly). Just switched back to another kernel and using the kernel server, and both lockd and statd both seem to be running OK, and no more locking errors on the clients. Unfortunately, it still hasn't fixed my other ongoing problem http://lists.debian.org/debian-user/2005/06/msg03111.html with symlinks not working on exported filesystems, but it's a step in the right direction...! Thanks for your help Marty, it set me on the right track! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] D'oh, fixed the problem by using relative paths when creating the symlink rather than absolute ones. So long as the exports are all mounted in the same directory on the client the symlinks work fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFS problems
Stephen Tait wrote: I've just been rejigging my file server following the upgrade to Sarge and have finally tried to sort out some niggling problems. Mainly, lockd doesn't seem to be running - I see the following entries all the time in my client machines (all gentoo): nfs warning: mount version older than kernel nsm_mon_unmon: rpc failed, status=-13 lockd: cannot monitor 192.168.1.10 lockd: failed to monitor 192.168.1.10 nsm_mon_unmon: rpc failed, status=-13 lockd: cannot monitor 192.168.1.10 lockd: failed to monitor 192.168.1.10 Googling about tells me that lockd should be running from the kernel, but as far as I can tell it isn't: tamora:/usr/src/linux# rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 8601142441 udp786 8601142441 tcp788 132 udp 2049 nfs 132 tcp 2049 nfs 151 udp925 mountd 152 udp925 mountd 151 tcp928 mountd 152 tcp928 mountd 1000241 udp641 status 1000241 tcp644 status ...and neither is statd or rquotad (although I don't think I need this). I'm led to believe that because I use a custom kernel (built from debian sources 2.6.8) I should use the userspace kernel server (nfs-user-server) and not the nfs-kernel-server I previously had installed (now uninstalled, but it's init script and config remain). No, kernel NFS can be either compiled or loaded as a module into a custom kernel. But the userspace daemons (/sbin/rpc.lockd and /sbin/rpc.statd) don't seem to want to start even when I call them from the command line. A quick grep through my kernel config suggests this is because lockd is supposedly built into the kernel; tamora:/usr/src/linux# cat .config | grep -i lockd CONFIG_LOCKD=y CONFIG_LOCKD_V4=y My kernel just shows the first option, and I'm not using the kernel server. Although I can't for the life of me find the option in menuconfig (maybe due to me copying the .config over from my old 2.4 installation...? But I can't find the option in 2.4's menuconfig either). I found it by enabling the Show All Options option while running make xconfig. Using that option I also found that in order to enable CONFIG_LOCKD_V4, I first had to enable NFS server support (NFSD) and then NFSv3. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems
Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 From my experience it has to look like this: /cdrom 192.168.2.30/255.255.255.255(ro) 192.168.2.30 is the ip address allowed to remote mount the cdrom 255.255.255.255 is the netmask. In this case is only a host (ro) is the option that tell to the nfs server to export read-only Fabio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems
no change. same results. -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi On Thu, 15 Mar 2001, Fabio Massimo Di Nitto wrote: Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 From my experience it has to look like this: /cdrom 192.168.2.30/255.255.255.255(ro) 192.168.2.30 is the ip address allowed to remote mount the cdrom 255.255.255.255 is the netmask. In this case is only a host (ro) is the option that tell to the nfs server to export read-only Fabio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems
On Wed, 14 Mar 2001, Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 and the client's fstab contains 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0 i on the server, i then did... /etc/init.d/nfs-server reload and mounting on the client reports grickle:~# mount /nfscdrom mount: thneed:/test failed, reason given by server: Permission denied Hmm, you try to mount /cdrom on the server, but it reports that you try to mount /test. Have you loaded nfs-common-utils? What does 'rpcinfo -p' on the server say? At least rpc.mountd and rpc.nfsd should have been loaded. Also did I discover that sometimes portmapper is not load automatically, so by doing: /etc/init.d/portmapper restart /etc/init.d/nfs-common restart /etc/init.d/nfs-server restart and rpcinfo -p should display something like: 1 2 tcp 111 portmapper 1 2 ucp 111 portmapper 389 2 tcp ??? mountd 389 2 ucp ??? mountd 385 2 tcp ??? nfsd 385 2 ucp ??? nfsd I cannot remember exactly, just check the most right colom. Greetz, Sebastiaan could someone please elighten me on what the heck i'm doing wrong? -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems
oh, the test thing is because initially i thought it might have been a problem with trying to export a cdrom. and i made a test dir and export. anyhow, i switched it back to the cdrom in both cases. thneed:~# rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000211 udp 32768 nlockmgr 1000213 udp 32768 nlockmgr 1000241 udp895 status 1000241 tcp897 status 132 udp 2049 nfs 132 tcp 2049 nfs 151 udp906 mountd 152 udp906 mountd 151 tcp909 mountd 152 tcp909 mountd the server shows that, so it looks like everything is running alright to me, and the client still has grickle:~# mount /nfscdrom mount: 192.168.1.10:/cdrom failed, reason given by server: Permission denied i never had any problems with the nfs-kernel-server, but since this is a 2.4 machine, i don't think thats an option, is it? -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi On Thu, 15 Mar 2001, Sebastiaan wrote: On Wed, 14 Mar 2001, Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 and the client's fstab contains 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0 i on the server, i then did... /etc/init.d/nfs-server reload and mounting on the client reports grickle:~# mount /nfscdrom mount: thneed:/test failed, reason given by server: Permission denied Hmm, you try to mount /cdrom on the server, but it reports that you try to mount /test. Have you loaded nfs-common-utils? What does 'rpcinfo -p' on the server say? At least rpc.mountd and rpc.nfsd should have been loaded. Also did I discover that sometimes portmapper is not load automatically, so by doing: /etc/init.d/portmapper restart /etc/init.d/nfs-common restart /etc/init.d/nfs-server restart and rpcinfo -p should display something like: 1 2 tcp 111 portmapper 1 2 ucp 111 portmapper 389 2 tcp ??? mountd 389 2 ucp ??? mountd 385 2 tcp ??? nfsd 385 2 ucp ??? nfsd I cannot remember exactly, just check the most right colom. Greetz, Sebastiaan could someone please elighten me on what the heck i'm doing wrong? -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems
On Wed, Mar 14, 2001 at 10:02:29PM -0800, Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 and the client's fstab contains 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0 i on the server, i then did... /etc/init.d/nfs-server reload and mounting on the client reports grickle:~# mount /nfscdrom mount: thneed:/test failed, reason given by server: Permission denied could someone please elighten me on what the heck i'm doing wrong? Did you try adding portmap: 192.168.1.10 to /etc/hosts.allow? Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) I'm going to exit now since you don't want me to replace the printcap. If you change your mind later, run -- magicfilter config script
Re: nfs problems
On Wed, 14 Mar 2001, Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 and the client's fstab contains 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0 i on the server, i then did... /etc/init.d/nfs-server reload and mounting on the client reports grickle:~# mount /nfscdrom mount: thneed:/test failed, reason given by server: Permission denied could someone please elighten me on what the heck i'm doing wrong? -- Forrest English http://truffula.net [...] Check 'showmount -e' on server - you'll see active exports and your '/cdrom' should be between them. If it's not - check /etc/exports (i think you should add (ro) to the cdrom export - but i'm not sure) and reload portmap and nfsd (i don't know why but sometimes reloading only nfsd didn't work). But this is probably OK - so check logs on server - there you should find the answer (look for mountd and nfsd). It's also possible that you put something in /etc/hosts.allow or hosts.deny that refuses mounting - take a look at these files. And as i remember - rules of access for portmap have to be given with IP-adresses - not domain names. Eg. /etc/hosts.allow This will not work - portmap: host.domain : ALLOW ALL:ALL:DENY - and this should be OK. - portmap: 192.168.1.1 : ALLOW ALL:ALL:DENY - I hope it'll help. tom.
Re: nfs problems
Hi, I just remembered something: nfs might not let you export cdroms. I had this with redhat about a year ago. You also can not proxy nfs (that is: install a nfs server and mount a nfs mounted filesystem). I do not know what the status is now. I do know that the exports file is vary annoying, especially with spaces. Try adding (ro) as option. On Thu, 15 Mar 2001, Forrest English wrote: oh, the test thing is because initially i thought it might have been a problem with trying to export a cdrom. and i made a test dir and export. anyhow, i switched it back to the cdrom in both cases. thneed:~# rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000211 udp 32768 nlockmgr 1000213 udp 32768 nlockmgr 1000241 udp895 status 1000241 tcp897 status 132 udp 2049 nfs 132 tcp 2049 nfs 151 udp906 mountd 152 udp906 mountd 151 tcp909 mountd 152 tcp909 mountd the server shows that, so it looks like everything is running alright to me, and the client still has grickle:~# mount /nfscdrom mount: 192.168.1.10:/cdrom failed, reason given by server: Permission denied i never had any problems with the nfs-kernel-server, but since this is a 2.4 machine, i don't think thats an option, is it? Why not? I have the least problems with the kernel server now that I am running 2.4. The patches for 2.2.18 did not work well enough. Greetz, Sebastiaan -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi On Thu, 15 Mar 2001, Sebastiaan wrote: On Wed, 14 Mar 2001, Forrest English wrote: ok, here's what i do on the server. /etc/exports file contains /cdrom 192.168.2.30 and the client's fstab contains 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0 i on the server, i then did... /etc/init.d/nfs-server reload and mounting on the client reports grickle:~# mount /nfscdrom mount: thneed:/test failed, reason given by server: Permission denied Hmm, you try to mount /cdrom on the server, but it reports that you try to mount /test. Have you loaded nfs-common-utils? What does 'rpcinfo -p' on the server say? At least rpc.mountd and rpc.nfsd should have been loaded. Also did I discover that sometimes portmapper is not load automatically, so by doing: /etc/init.d/portmapper restart /etc/init.d/nfs-common restart /etc/init.d/nfs-server restart and rpcinfo -p should display something like: 1 2 tcp 111 portmapper 1 2 ucp 111 portmapper 389 2 tcp ??? mountd 389 2 ucp ??? mountd 385 2 tcp ??? nfsd 385 2 ucp ??? nfsd I cannot remember exactly, just check the most right colom. Greetz, Sebastiaan could someone please elighten me on what the heck i'm doing wrong? -- Forrest English http://truffula.net When we have nothing left to give There will be no reason for us to live But when we have nothing left to lose You will have nothing left to use -Fugazi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nfs problems - read/write, restarting nfs_damon
On Thursday 30 November 2000 12:07, robert_wilhelm_land wrote: two linux boxes are connected via nfs to each other: MINI (kernel_2.2.17) -- GOOFY (kernel_2.0.38) the /etc/exports on GOOFY: /home/rland MINI(rw) After rebooting I do a MINI:/home/rland# mount -t nfs GOOFY:/home/rland ./testdir after this ./testdir changes from: drwxr-sr-x2 rlandrland4096 Nov 30 18:38 testdir to drwxrwxr-x 24 1001 users4096 Nov 27 12:17 testdir You have the user and group rland on one of the computer, but not on the other. The 1001 is a user number, and that machine has no user associated with that number. Look into NIS (I've never used it, but it's the thing you want) to keep both machines' /etc/group and /etc/passwd files the same (it's nice in that you get to change the password for a user only once, but both machines will use that new password). If you don't want to mess with that, then you have to adduser rland on the machine where that user doesn't exist. Any other users you add will have to be added to both machines (in the same order, numbers are assigned first-come, first-served) to keep this stuff in sync. I do this at home, because it's just me and my wife. -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: nfs problems - read/write, restarting nfs_damon
Robert Guthrie [EMAIL PROTECTED] wrote: On Thursday 30 November 2000 12:07, robert_wilhelm_land wrote: two linux boxes are connected via nfs to each other: MINI (kernel_2.2.17) -- GOOFY (kernel_2.0.38) the /etc/exports on GOOFY: /home/rland MINI(rw) After rebooting I do a MINI:/home/rland# mount -t nfs GOOFY:/home/rland ./testdir after this ./testdir changes from: drwxr-sr-x2 rlandrland4096 Nov 30 18:38 testdir to drwxrwxr-x 24 1001 users4096 Nov 27 12:17 testdir You have the user and group rland on one of the computer, but not on the other. The 1001 is a user number, and that machine has no user associated with that number. Look into NIS (I've never used it, but it's the thing you want) to keep both machines' /etc/group and /etc/passwd files the same (it's nice in that you get to change the password for a user only once, but both machines will use that new password). If you don't want to mess with that, then you have to adduser rland on the machine where that user doesn't exist. Any other users you add will have to be added to both machines (in the same order, numbers are assigned first-come, first-served) to keep this stuff in sync. I do this at home, because it's just me and my wife. Keeping temporärly away from NIS I added user rland on MINI to group users. On GOOFY user rland belongs only to group users. After this rland on MINI may view the files and do a ls -l, but he cannot write to the mounted nfs dir. Even after rereading you help - I couldn't figure out what I had missed. Would you kindly give me more assistance? Robert
Re: nfs problems - read/write, restarting nfs_damon
On Thursday 30 November 2000 13:04, robert_wilhelm_land wrote: Keeping temporärly away from NIS I added user rland on MINI to group users. On GOOFY user rland belongs only to group users. After this rland on MINI may view the files and do a ls -l, but he cannot write to the mounted nfs dir. Even after rereading you help - I couldn't figure out what I had missed. Would you kindly give me more assistance? I think the best advice I can give at this point is to carefully read the mount man page. There are a lot of options there that may come into play. I can't think of which options you might need, but my guess is that you need to mount that directory with different options related to permissions and/or users. The other man pages of interrest might be exports for the machine that is serving the nfs directory. Maybe the NFS howto would be a good place to look too. -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: nfs problems: can't find request slot
Colin == Colin McMillen [EMAIL PROTECTED] writes: Colin Anyone have any ideas on what's going wrong, and what I can Colin try to fix it? I sometimes get these errors, and then suddenly everything comes good. ie. the same behaviour I might expect if I pulled the network plug out for 60 seconds... Sorry, I don't know why this should happen. Somebody once suggested it might help to upgrade my coaxial network to a twisted pair network though. -- Brian May [EMAIL PROTECTED]
Re: NFS problems, cannot mount-permission denied
One possibility is that the client is not named what you think. Try to telnet from the client to the NFS server and do a 'who' and see what it thinks the clients hostname is. You are exporting to myclientname but the server may be seeing it as myclientname.domain.nam and that won't match causing the 'permission denied' error. Good luck, Frank --On Thursday, December 24, 1998, 3:24 PM +0100 John Stevenson [EMAIL PROTECTED] wrote: I am trying to set up NFS between to Debian Linux 'Hamm' boxes. I have followed all the instructions in the NFS Howto, but always run into a permissions problem. * edited /etc/exports file and added the following line: /nfs/export myclientname(rw) mount: myserver:/nfs/export failed, reason given by server: Permission denied Does any one have any clues as to what is wrong
Re: NFS problems with Debian server and Solaris client
Jean Pierre LeJacq [EMAIL PROTECTED] writes: I'm having problems getting Solaris 2.5.1 to use the Debian NFS server. Read only file systems work fine. On read-write file we'll go the other way round in the near future ;-) but Solaris uses a new nfs Version (3) instead of 2. Perhaps you can deactivate the new nfs and only use the old one. Another thing is the new CacheFS - perhaps it helps if you deacticate it. Hope it helps Christian -- Christian Leutloff, Aachen, Germany eMail: [EMAIL PROTECTED] http://www.oche.de/~leutloff/ Debian/GNU Linux! Mehr unter http://www.debian.org/ pgpnr5sitQ8LC.pgp Description: PGP signature
Re: NFS problems with Debian server and Solaris client
I do have similar problems serving SGI machines. It might depend on the way a file system is mounted e.g. hard vs. soft, but I'am not sure, still testing ... Markus Diesmann -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
