Re: nfs problem [FIXED?]
On 01/02/2016 10:06 AM, Glenn English wrote: Beats me, but it's working. I modified the line in /etc/exports (all on one line) to: /home/ghe/Finances 192.168.3.0/255.255.255.0(rw,no_root_squash,no_subtree_check) That isn't exactly as suggested, but there were mild complaints about not having anything about subtree_check. and in fstab on the client: sbox.slsware.lan:/home/ghe/Finances /home/ghe/Finances nfs user,nfsvers=3,exec,_netdev00 I'm thinking that 'nfsvers=3' might have done it, or maybe hand writing the export line containing the dotted quads for the IP/mask. Or maybe that I printed many pages of documentation. I really don't know; it just magically started working. I hate it when variables > 1. Anyway, thank you all. I got my gnucash file in one place, on one server, but available to me everywhere on the LAN. And the next file will be a whole lot easier... -- Glenn English
Re: nfs problem
> On Jan 1, 2016, at 3:11 PM, Brandon Vincent wrote: > > I would return the server's idmapd.conf back to the default > configuration (nobody:nogroup) and make sure that the idmapd service > is running on both the server and the client. Make sure the domain > matches in idmapd.conf on both the server and client. Hmmm. Nobody told me before that I needed idmapd on both ends. Bears looking into. Thanks. -- Glenn English
Re: nfs problem
> On Jan 1, 2016, at 4:41 PM, Pier wrote: > > It was ages I didn't write to the list but nfs always arouse curiosity ;) > First try to force nfsv3 to see if permissions are ok (v3 uses numeric > uid/gid) with 'mount -o vers=3'. > If this works and you want to use nfsv4 then make sure the configuration of > idmap are the same on both the nfs server and nfs client (make sure the > domain is the same, you can leave the rest the original). > Also make sure the users/groups are available/the same on both the nfs > server/client. > > Hope this helps. So do I :-) I'm fine with v3. I'll try them. -- Glenn English
Re: nfs problem
> On Jan 2, 2016, at 2:56 AM, Anders Andersson wrote: > > 1) Ditch webmin, I don't know what it is but it seems to break > something that should be pretty simple to set up, without giving any > feedback. Webmin's one of those web-based GUI admin things. I use it because it usually does well, and it makes many configs quite a bit easier. It saved my life many times when I first hit Linux and IP networking. In the past, Webmin's managed to make NFS work for me, but this seems to be one of those probs that require vi and a plea to the list... > 2) If the problem involves some files that do not exist, please list > them, maybe it's a clue that something important is missing. I've looked at so many on the 'Net that I don't remember where I looked or what they were. > 3) NFS is well documented in the man-pages, but has a pathetic > documentation online. Try "man nfs" and "man exports". Done, looks hopeful. > 4) As somone else mentioned, do not mess with idmapd, since you have > the UIDs synced already. I'll put its config back to where it was :-) > 5) Until a few weeks ago my main NFS server was wheezy, but I am now > using stretch. My files looks like this: > > On the (stretch) server: /etc/exports contains: > /srv/stuff 1.2.3.0/24(sec=sys,rw,no_subtree_check,mp,root_squash) > > On the (jessie) clients: /etc/fstab contains: > name_of_server:/srv/stuff /stuff nfs4 _netdev,rw,auto,bg > > You shouldn't have to change any other files, really, but I can't > remember if this has something that's not supported on wheezy. Very useful info -- different from what Webmin wrote. I'm a bit far from having an NFS export mounted at boot, though. When it works by hand, I'll put it in. Thank you, Anders. -- Glenn English
Re: nfs problem
On Fri, Jan 1, 2016 at 10:30 PM, Glenn English wrote: > Come on folks! > > Consider a modified Drake equation: (number on this list) * (date) * (% not > hungover) * (% who understand NFS) * (% willing to help out a bewildered > computer geek) == (surely > 0), no? > > OK. Leave out (date) and (% not hungover), and tell me what I've done wrong... > >> On Dec 31, 2015, at 4:56 PM, ghe wrote: >> >> I'm trying to get NFS going with a Wheezy server and a Jessie client using >> Webmin and vi. It connects, but mounts the directory and file with >> nobody:nogroup as the user:group (and nobody isn't set to universe >> read/write -- tried to do that, but NFS won't let me). >> >> I see from the 'Net that this is a common problem, but the solutions seem to >> involve (some) files/programs that don't exist on these machines. Nor in >> Aptitude. >> >> The UID:GID are identical on the server and the client, both numbers and >> text. I've tried both NFS4 and vanilla NFS. There seems to be no difference. >> >> I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a >> new user (gheqw). Now ls says the directory on the client is owned by >> gheqw:nogroup. That doesn't make any sense to me at all. >> >> When I turn off the NFS mount at the server, the directory on the client >> goes back to being owned by me, and the file disappears (both expected >> behavior). >> >> There are too many variables here: 2 computers, many files, and far too many >> [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the config >> files (whichever they are). Anybody know exactly what to say, in which >> file(s) on which computer(s), to deal with this? Ok, I have a couple of suggestions, which should not necessarily be implemented in this order. :) 1) Ditch webmin, I don't know what it is but it seems to break something that should be pretty simple to set up, without giving any feedback. 2) If the problem involves some files that do not exist, please list them, maybe it's a clue that something important is missing. 3) NFS is well documented in the man-pages, but has a pathetic documentation online. Try "man nfs" and "man exports". 4) As somone else mentioned, do not mess with idmapd, since you have the UIDs synced already. 5) Until a few weeks ago my main NFS server was wheezy, but I am now using stretch. My files looks like this: On the (stretch) server: /etc/exports contains: /srv/stuff 1.2.3.0/24(sec=sys,rw,no_subtree_check,mp,root_squash) On the (jessie) clients: /etc/fstab contains: name_of_server:/srv/stuff /stuff nfs4 _netdev,rw,auto,bg You shouldn't have to change any other files, really, but I can't remember if this has something that's not supported on wheezy.
Re: nfs problem
On Friday, 1 January 2016, 21:57, Glenn English wrote: Come on folks! Consider a modified Drake equation: (number on this list) * (date) * (% not hungover) * (% who understand NFS) * (% willing to help out a bewildered computer geek) == (surely > 0), no? OK. Leave out (date) and (% not hungover), and tell me what I've done wrong... > On Dec 31, 2015, at 4:56 PM, ghe wrote: > > I'm trying to get NFS going with a Wheezy server and a Jessie client using > Webmin and vi. It connects, but mounts the directory and file with > nobody:nogroup as the user:group (and nobody isn't set to universe read/write > -- tried to do that, but NFS won't let me). [big cut] It was ages I didn't write to the list but nfs always arouse curiosity ;)First try to force nfsv3 to see if permissions are ok (v3 uses numeric uid/gid) with 'mount -o vers=3'.If this works and you want to use nfsv4 then make sure the configuration of idmap are the same on both the nfs server and nfs client (make sure the domain is the same, you can leave the rest the original).Also make sure the users/groups are available/the same on both the nfs server/client. Hope this helps. Pier PS: you can check which version of nfs is used in /proc/mounts
Re: nfs problem
On Thu, Dec 31, 2015 at 4:56 PM, ghe wrote: > I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a > new user (gheqw). Now ls says the directory on the client is owned by > gheqw:nogroup. That doesn't make any sense to me at all. I would return the server's idmapd.conf back to the default configuration (nobody:nogroup) and make sure that the idmapd service is running on both the server and the client. Make sure the domain matches in idmapd.conf on both the server and client. Brandon Vincent
Re: nfs problem
Come on folks! Consider a modified Drake equation: (number on this list) * (date) * (% not hungover) * (% who understand NFS) * (% willing to help out a bewildered computer geek) == (surely > 0), no? OK. Leave out (date) and (% not hungover), and tell me what I've done wrong... > On Dec 31, 2015, at 4:56 PM, ghe wrote: > > I'm trying to get NFS going with a Wheezy server and a Jessie client using > Webmin and vi. It connects, but mounts the directory and file with > nobody:nogroup as the user:group (and nobody isn't set to universe read/write > -- tried to do that, but NFS won't let me). > > I see from the 'Net that this is a common problem, but the solutions seem to > involve (some) files/programs that don't exist on these machines. Nor in > Aptitude. > > The UID:GID are identical on the server and the client, both numbers and > text. I've tried both NFS4 and vanilla NFS. There seems to be no difference. > > I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a > new user (gheqw). Now ls says the directory on the client is owned by > gheqw:nogroup. That doesn't make any sense to me at all. > > When I turn off the NFS mount at the server, the directory on the client goes > back to being owned by me, and the file disappears (both expected behavior). > > There are too many variables here: 2 computers, many files, and far too many > [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the config > files (whichever they are). Anybody know exactly what to say, in which > file(s) on which computer(s), to deal with this? > > T much IA... > > -- > Glenn English -- Glenn English
nfs problem
I'm trying to get NFS going with a Wheezy server and a Jessie client using Webmin and vi. It connects, but mounts the directory and file with nobody:nogroup as the user:group (and nobody isn't set to universe read/write -- tried to do that, but NFS won't let me). I see from the 'Net that this is a common problem, but the solutions seem to involve (some) files/programs that don't exist on these machines. Nor in Aptitude. The UID:GID are identical on the server and the client, both numbers and text. I've tried both NFS4 and vanilla NFS. There seems to be no difference. I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a new user (gheqw). Now ls says the directory on the client is owned by gheqw:nogroup. That doesn't make any sense to me at all. When I turn off the NFS mount at the server, the directory on the client goes back to being owned by me, and the file disappears (both expected behavior). There are too many variables here: 2 computers, many files, and far too many [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the config files (whichever they are). Anybody know exactly what to say, in which file(s) on which computer(s), to deal with this? T much IA... -- Glenn English
Re : nfs problem
Strangely, putting a dns for the local zone (and forwarder for the rest) improves the situation. No cannot monitor in kern.log anymore ... De : Bob Proulx À : debian-user@lists.debian.org Envoyé le : Mardi 20 Septembre 2011 21h46 Objet : Re: nfs problem Stephane Durieux wrote: > I have messages like this in logs: > lockd cannot monitor ip_address > and also messages about statd The lockd: cannot monitor messages are due to the kernel being unable to communicate with the rpc.statd process. That usually indicates that the rpc.statd is not running, possibly due to it crashing. NFS is a stateless protocol. But file locks are inherently stateful. To maintain file locks some auxilary programs are used such as the rpc.statd. Check that the rpc.statd is running. ps -e | grep rpc.statd It is started from the nfs-common service. You may have to restart it. # service nfs-common restart Problems with NFS locking has been a problem forever. > But client ip are present in /etc/hosts. This has nothing to do with host names or DNS resolution. > Do I need to put a DNS server for reverse resolution even for > private ip, it s a pity No. Not for NFS. But generally it is always a good idea that names resolve to addresses and the reverse of resolving addresses to names also works. Bob
Re: nfs problem
Stephane Durieux wrote: > I have messages like this in logs: > lockd cannot monitor ip_address > and also messages about statd The lockd: cannot monitor messages are due to the kernel being unable to communicate with the rpc.statd process. That usually indicates that the rpc.statd is not running, possibly due to it crashing. NFS is a stateless protocol. But file locks are inherently stateful. To maintain file locks some auxilary programs are used such as the rpc.statd. Check that the rpc.statd is running. ps -e | grep rpc.statd It is started from the nfs-common service. You may have to restart it. # service nfs-common restart Problems with NFS locking has been a problem forever. > But client ip are present in /etc/hosts. This has nothing to do with host names or DNS resolution. > Do I need to put a DNS server for reverse resolution even for > private ip, it s a pity No. Not for NFS. But generally it is always a good idea that names resolve to addresses and the reverse of resolving addresses to names also works. Bob signature.asc Description: Digital signature
nfs problem
Hello, I am encountering a problem with nfs on debian squeeze. I have messages like this in logs: lockd cannot monitor ip_address and also messages about statd But client ip are present in /etc/hosts. On the client the mount process works. The only problem is locking (application like firefox for example) and when several stations are on the network, the collaspe begin Has anybody an idea of what happens ? Do I need to put a DNS server for reverse resolution even for private ip, it s a pity Thanks
Re: nfs problem
Kurian Thayil wrote: > Hi, > > If I can remember correctly. Include the option no_root_squash > in /etc/exports of B. It will be like, > > /home/storage/video A(rw,sync,subtree_check,no_root_squash) > > You will be able to read-write as root if you include this > option. This did not really work. To my amazement, the following drastic simplification worked: on B: /etc exports reads /home/storage/video A(async) C(async) A user on the home net (desktop machine A or C) can mount, read, and write the shared directory now. nfs remains mysterious. But I am slowly gaining experience, now my home has become 100% Debian (two desktops and a gateway/server/firewall). Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
Hi, If I can remember correctly. Include the option no_root_squash in /etc/exports of B. It will be like, /home/storage/video A(rw,sync,subtree_check,no_root_squash) You will be able to read-write as root if you include this option. Regards, Kurian Mathew Thayil. On 10/30/08, Mirco Piccin <[EMAIL PROTECTED]> wrote: > Hi, > >> Machines A and B both run Debian. There are no firewall rules >> blocking any kind of traffic A<-->B. > >> I try to mount, by means of nfs, a directory of B to a mount point >> on A, read-write. > >> I can read the contents of /home/storage/video on B. But I cannot >> write anything to it. I keep getting the message "read-only >> filesystem". > > i'm not actual using NFS, but i remember that you must have the same > user and group id on both pc, or you will not able to do the job as > you describe. > > hope this helps you! > Regards > M > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
Hi, > Machines A and B both run Debian. There are no firewall rules > blocking any kind of traffic A<-->B. > I try to mount, by means of nfs, a directory of B to a mount point > on A, read-write. > I can read the contents of /home/storage/video on B. But I cannot > write anything to it. I keep getting the message "read-only > filesystem". i'm not actual using NFS, but i remember that you must have the same user and group id on both pc, or you will not able to do the job as you describe. hope this helps you! Regards M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nfs problem
Machines A and B both run Debian. There are no firewall rules blocking any kind of traffic A<-->B. I try to mount, by means of nfs, a directory of B to a mount point on A, read-write. /etc/exports in B has: /home/storage/video A(rw,sync,subtree_check) /etc/fstab in A has: B:/home/storage/video /mountB nfs \ user,rw,intr,rsize=8192,wsize=8192,timeo=14,noauto 0 0 If I call (on A) mount /mountB I can read the contents of /home/storage/video on B. But I cannot write anything to it. I keep getting the message "read-only filesystem". I hope there are some nfs experts here who can shed some light. Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem -- SOLVED!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 And thanks also to Matthew M. -- sorry Matthew. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIkNNElNlJzOkJmTcRAi6IAJ92a316VPCAh0E47K4+J6wadeBCbgCggba9 GThDY5qkC/DgJW3SOz6bQcs= =1zh8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem -- SOLVED!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Samad put me on the right track to the solution. See comments in line below. >> Other factors which may have a bearing on the situation: the BDS >> computer is a P4; whereas the SOL is a dual core on a Foxconn >> motherboard. Several other things do not work properly in SOL, such as >> mounting and unmounting CF cards; so I wonder if there is something >> wrong with the Foxconn BIOS. There has been some noise on line recently >> about Foxconn's unfriendliness to Linux; for on Foxconn board model (not >> mine) somebody disected the BIOS and found out why. When he raised the >> issue with Foxconn they were upset at being found out but did not care >> whether Linux worked with Foxconn boards or not. Caveat emptor. > > I would be rather supprised if a boggy bios stopped nfs mounting, as long > as ping and other ip was working okay. Yes, true in this case, but I think I still have issues respecting this board and its BIOS -- subject for a separate thread perhaps. > Also have a look from each server to the other server with showmounts -e > I did not know about this command, which by the way is "showmount", so I read its man page. Running "showmount -e SOL" on BDS returned the directories exported from BDS, not those exported from SOL -- most peculiar. I then got the bright idea to run "showmount -e 192.168.0.114", 114 being the IP address of the SOL box. This time the command returned the directories exported from SOL. So what it going on? By running ifconfig in both boxes I verified their IP addresses. I checked the /etc/hosts file in both to verify that the right hostnames were assigned to the right IP addresses. They were. I paid particular attention to the BDS:/etc/hosts file, because I assumed that the problem must reside there. Finally I noticed that the local loopback alias was SOL, not BDS. The box now called BDS used to be called SOL. When I changed the name I changed the name assigned to the IP address of the new BDS (old SOL) but had neglected to change the loopback alias. So I changed it, and BDS can now access the directories exported from SOL. I don't fully understand the loopback, but the fact that I had the loopback alias wrong obviously explains why other things had not worked, such as accessing html files from a browser using the alias rather than "localhost". Thanks to Thomas P. and Alex S. for their help. Regards, Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIkNLQlNlJzOkJmTcRAkyQAJ9XjDfyr+kSV74ksT6bNng2APu7zQCePnK2 d61lQ9w66qLgfN2CraL4Hzs= =UdRM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem
some thoughts inline On Tue, Jul 29, 2008 at 12:13:28PM -0400, Ken Heard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > In response to my message of 2008-07-28 on this subject M. Preud'homme > rightly intimated that I should have provided more information so that > he (and others?) could help me. So, here is the information he asked me > for, as well as the output of the "strace mount -a" command. > [snip] > Other factors which may have a bearing on the situation: the BDS > computer is a P4; whereas the SOL is a dual core on a Foxconn > motherboard. Several other things do not work properly in SOL, such as > mounting and unmounting CF cards; so I wonder if there is something > wrong with the Foxconn BIOS. There has been some noise on line recently > about Foxconn's unfriendliness to Linux; for on Foxconn board model (not > mine) somebody disected the BIOS and found out why. When he raised the > issue with Foxconn they were upset at being found out but did not care > whether Linux worked with Foxconn boards or not. Caveat emptor. I would be rather supprised if a boggy bios stopped nfs mounting, as long as ping and other ip was working okay > > There are also other differences which I should not think contribute to > the problem. In SOL only the /home directories and files are encrypted. > SOL uses the XFS file system; BDS has ext3. > > I apologize for the length of this message, but it was necessary to > provide the requested information. I hope it will be worthwhile. > > Regards, Ken Heard, Toronto, Canada > - [snip] have you looked at /etc/hosts.allow and deny. check out /var/log/auth.log and daemon.log. Usually the only permissioning problems are access to the path I think full path access is need ie for an export of /home/alex/test I would need access to /home and /home/alex and /home/alex/test. Another thing I do when trying to diagnose this is tcpdump, turn off all the other mounts and start up tcpdump to capture the packets between the servers. (u could also use wireshark or tshark) Also have a look from each server to the other server with showmounts -e -- "He understands the need for a timely write of the constitution." - George W. Bush 04/28/2005 Washington, DC on Prime Minister Iyad Allawi of Iraq signature.asc Description: Digital signature
Re: NFS problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As Matthew Moore suggested, after reading the relevant manual page to see what command exportfs -r does, I ran on the server machine (SOL) exportfs -rv, which returned the following: exporting 192.168.0.0/24:/home/ken/mozilla exporting 192.168.0.0/24:/home/ken/images exporting 192.168.0.0/24:/home/ken/docs I then ran on the client machine (BDS) mount -a. Unfortunately is returned the same message as before: mount failed: reason given by server: permission denied. Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIj4/PlNlJzOkJmTcRApTSAJ9n2tDLS4A67Zlt9opxsfMbMnqDjACfWx34 rL8dRERgvONCCIIXmct8Q+U= =L/2P -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem
Hello, You might try running $ exportfs -r on the host computer. MM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In response to my message of 2008-07-28 on this subject M. Preud'homme rightly intimated that I should have provided more information so that he (and others?) could help me. So, here is the information he asked me for, as well as the output of the "strace mount -a" command. Both the subject computers use Etch. One computer is named SOL, which is used regularly by user ken; so all ken's user files are in SOL. In SOL the permissions for the directory /home/ken -- and all the directories the next level down in /home/ken -- are drwxrwx---. The other computer is called BDS, which is regularly used by user martin; so all of his user files are in BDS. In BDS the permissions for the directory /home/martin -- and all the directories the next level down in /home/martin -- are drwxrwx---. In order for user martin to access his files on computer BDS by logging in to computer SOL, file BDS:/etc/exports reads as follows: /home/martin/docs 192.168.0.0/24(rw,no_subtree_check) /home/martin/ice192.168.0.0/24(rw,no_subtree_check) /home/martin/images-elph192.168.0.0/24(rw,no_subtree_check) /home/martin/images-m 192.168.0.0/24(rw,no_subtree_check) The output of command exportfs run on the BDS computer is consequently: /home/martin/images-elph 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /home/martin/images-m 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /home/martin/docs 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /home/martin/ice 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) In the SOL computer, the relevant lines of /etc/fstab are as follows: # BDS:/home/martin/docs /home/martin/docs nfs defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft 0 0 BDS:/home/martin/ice/home/martin/icenfs defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft 0 0 BDS:/home/martin/images-elph/home/martin/images-elphnfs defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft 0 0 BDS:/home/martin/images-m /home/martin/images-m nfs defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft 0 0 This arrangement works; martin, when logged on in SOL has access to his files which physically are located in the BDS computer. It is the arrangement is the other direction which does not work. File SOL:/etc/exports is as follows: /home/ken/docs 192.168.0.0/24(rw,no_subtree_check) /home/ken/images192.168.0.0/24(rw,no_subtree_check) /home/ken/mozilla 192.168.0.0/24(rw,no_subtree_check) The output of command exportfs run on the SOL computer is consequently: /home/ken/mozilla 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /home/ken/images 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /home/ken/docs 192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534) In the BDS computer, the relevant lines of /etc/fstab are as follows: # SOL:/home/ken/docs /home/ken/docs nfs defaults,noatime,bg,retry=5,rsize=8192,wsize=8192,soft 0 0 SOL:/home/ken/mozilla /home/ken/mozilla nfs defaults,noatime,bg,retry=5,rsize=8192,wsize=8192,soft 0 0 (I chose for the time being not to mount in BDS directory SOL:/home/ken/images.) Both SOL and BDS are turned off overnight. BDS is usually booted first the following morning; SOL is usually booted about three minutes later. Once both are booted, SOL can find the directories exported from BDS; but BDS cannot find the directories exported from SOL. I could find nothing from the dmesg command or from the syslog file to relating to the NFS. After both computers have been booted but the export from SOL to BDS does not work, I am able to ping successfully from one computer to the other. Running command "mount -a" from root however returns the following: mount: none already mounted or /proc/bus/usb busy mount: according to mtab, procbususb is already mounted on /proc/bus/usb mount: SOL:/home/ken/docs failed, reason given by server: Permission denied mount: SOL:/home/ken/mozilla failed, reason given by server: Permission denied The output of command "strace mount -a" is appended to the end of this message after the horizontal line. I cannot understand it; I hope it means something useful for my problem to somebody. Other factors which may have a bearing on the situation: the BDS computer is a P4; whereas the SOL is a dual core on a Foxconn motherboard. Several other things do not work properly in SOL, such as mounting and unmounting CF cards; so I wonder if there is something wrong with the Foxconn BIOS. There has been some noise on line recently about Foxconn's unfriendliness to Linux; for on Foxconn board model (not mine) somebody
Re: NFS problem
Le lundi 28 juillet 2008, Ken Heard a écrit : > I have two boxes, one normally used by user A, and the other by user > B. I want to make it possible for user A to access his files from B's > computer, and vice versa. > > So, in each computer I amended > > 1) file /etc/exports to export the relative directories and restarted > nfs-kernel-server, and > > 2) amended file /etc/fstab to mount the the directories exported from > the other computer in directores having the same name as the exported > ones and ran mount -a. > > It is now possible for user A to log in on B's computer and see and > use his files, but not the reverse: B cannot log in on A's computer > and use his files. > > What I find strange is that the nfs settings on both computers are > absolutely identical. Both computers use Etch. The names and ids of > both users are the same; they both belong to the same group which has > identical name and id on both computers; and the permissions are the > same "drwxrwx---". Is it the permission of the directory you export ? And what about the rights of the file /etc/exports ? > > One computer is a P4; the other is a dual core. The export from the > P4 to the dual core works; but the export from the dual core to the > P4 does not. When I run mount -a on the P4 the following is returned > for each directory to be mounted: > > failed, reason given by server: Permission denied Maybe a strace on the mount command will show something. Else please provide ls -al outputs of /etc/exports and the directory exported and directory where it is mounted. > > After careful and extended experimentation I can't figure out why the > dual core cannot export. I no one can provide me advice to point to > why, perhaps I should file a bug report. > > Ken Heard Regards Thomas Preud'homme -- Why Debian : http://www.debian.org/intro/why_debian signature.asc Description: This is a digitally signed message part.
NFS problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have two boxes, one normally used by user A, and the other by user B. I want to make it possible for user A to access his files from B's computer, and vice versa. So, in each computer I amended 1) file /etc/exports to export the relative directories and restarted nfs-kernel-server, and 2) amended file /etc/fstab to mount the the directories exported from the other computer in directores having the same name as the exported ones and ran mount -a. It is now possible for user A to log in on B's computer and see and use his files, but not the reverse: B cannot log in on A's computer and use his files. What I find strange is that the nfs settings on both computers are absolutely identical. Both computers use Etch. The names and ids of both users are the same; they both belong to the same group which has identical name and id on both computers; and the permissions are the same "drwxrwx---". One computer is a P4; the other is a dual core. The export from the P4 to the dual core works; but the export from the dual core to the P4 does not. When I run mount -a on the P4 the following is returned for each directory to be mounted: failed, reason given by server: Permission denied After careful and extended experimentation I can't figure out why the dual core cannot export. I no one can provide me advice to point to why, perhaps I should file a bug report. Ken Heard -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIjiwblNlJzOkJmTcRAgGQAJwNSST44aBduivnWC4Al1Ss4DOYzgCfYIqp SCig4eEYqwfhny1DIznlwDk= =4Ftc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
Ding Honghui wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 nfs server 192.168.110.28 FilesystemSize Used Avail Use% Mounted on /dev/sdb1 2.2T 1.6T 473G 78% /home /etc/exports /home/nfs_for_217 192.168.110.27/255.255.255.255 (rw,sync,no_root_squash) nfs client FilesystemSize Used Avail Use% Mounted on 192.168.110.28:/home/nfs_for_217 170G -417G 474G - /data_nfs218 What's the problem? The field Used is -417 and field Use% is -. It's really strange.. thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiEZ04ACgkQJo9Njjkvy372fgCffo9vfZra66+rRzkwiaFDeAre Rn8AmwWST1LMI/Mknc51OSgjYauCAUrl =ndad -END PGP SIGNATURE- Sounds like a 32 vs. 64 bit int problem. Perhaps NFS isn't using the proper type for holding the relevant information for df to read? If you have access to a 64 bit capable system (laptop would be easiest, you could borrow for the test), you could boot using a live 64bit Debian CD, and do a mount of the NFS filesystem there. I expect it would show the proper sizes. -- Bob McGowan smime.p7s Description: S/MIME Cryptographic Signature
nfs problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 nfs server 192.168.110.28 FilesystemSize Used Avail Use% Mounted on /dev/sdb1 2.2T 1.6T 473G 78% /home /etc/exports /home/nfs_for_217 192.168.110.27/255.255.255.255 (rw,sync,no_root_squash) nfs client FilesystemSize Used Avail Use% Mounted on 192.168.110.28:/home/nfs_for_217 170G -417G 474G - /data_nfs218 What's the problem? The field Used is -417 and field Use% is -. It's really strange.. thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiEZ04ACgkQJo9Njjkvy372fgCffo9vfZra66+rRzkwiaFDeAre Rn8AmwWST1LMI/Mknc51OSgjYauCAUrl =ndad -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
Stephane Durieux wrote: > I have noticed that my clients are not declared in > /etc/hosts They won't need to be if you use DNS. But it is acceptable to list them in the local files. Local files override network DNS. > if I put them in /etc/hosts (and in nis table to be useful) > everything is find. You should not need to put hosts in NIS/YP and I recommend against it. NIS/YP for host information is obsolete. It is a holdover from before DNS became the dominant protocol. Having the same data in both places means that they can get out of sync and that leads to confusion. The DRY principle here is don't repeat yourself. > Nevertheless I don t understand how the nfs can make a > resolution via dns of a a client whith a private > address The NFS mountd will call gethostbyaddr(3). man 3 gethostbyaddr If the information is not available it will fail. But if dns is not available it will timeout trying to look it up. > Perhaps does the server reply it it s impossible and > everything is fine to log it Many server processes will look up client ip addresses that connect and try to log the name. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
On Fri, Aug 03, 2007 at 02:47:14PM +0200, Stephane Durieux wrote: > I have noticed that my clients are not declared in > /etc/hosts if I put them in /etc/hosts (and in nis > table to be useful) everything is find. > > Nevertheless I don t understand how the nfs can make a > resolution via dns of a a client whith a private > address > Perhaps does the server reply it it s impossible and > everything is fine to log it > /etc/nsswitch.conf (name service switch conf) has the line: hosts: files dns This means that when the resolver tries to find a host it will first look in the files on the system (e.g. /etc/hosts) before doing a dns search. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
--- Bob Proulx <[EMAIL PROTECTED]> a écrit : > Stephane Durieux wrote: > > client <-> server <-X-> internet > > > > That is exactly my issue . Excuse me for not being > > clear ! Anyway, has somebody a solution . > > I have read that client and server must be able to > > make a reverse resolution of the client and the > > server, but I am not sure of it and I don t have > an in > > depth knowledge of nfs . > > The nfs server will try to do a dns lookup of the > client ip address to > find the client hostname for the purpose of logging > this information > to the system logs. One the server can the client > IP address be > resolved? > > $ ssh server > $ host A.B.C.D # look up client IP address > > Does that succeed? Example: > > $ ssh www.example.com > host 208.77.188.166 > 166.188.77.208.in-addr.arpa domain name pointer > www.example.com. > > I suspect that your DNS on the server is not > functioning. > I have noticed that my clients are not declared in /etc/hosts if I put them in /etc/hosts (and in nis table to be useful) everything is find. Nevertheless I don t understand how the nfs can make a resolution via dns of a a client whith a private address Perhaps does the server reply it it s impossible and everything is fine to log it But thanks a lot, it s certainly the SYSTEM LOG that is implied ... I ll check it ... ...now it seems me a little bit more logical ! I was so lost that I have thought they were magical dark spirits behind this :) _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
Stephane Durieux wrote: > client <-> server <-X-> internet > > That is exactly my issue . Excuse me for not being > clear ! Anyway, has somebody a solution . > I have read that client and server must be able to > make a reverse resolution of the client and the > server, but I am not sure of it and I don t have an in > depth knowledge of nfs . The nfs server will try to do a dns lookup of the client ip address to find the client hostname for the purpose of logging this information to the system logs. One the server can the client IP address be resolved? $ ssh server $ host A.B.C.D # look up client IP address Does that succeed? Example: $ ssh www.example.com host 208.77.188.166 166.188.77.208.in-addr.arpa domain name pointer www.example.com. I suspect that your DNS on the server is not functioning. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
On Thu, Aug 02, 2007 at 01:46:40PM +0200, Stephane Durieux wrote: > --- Douglas Allan Tutty <[EMAIL PROTECTED]> a ?crit > > > > > > I encounter a problem whith my nfs stations. > > If the server has > > > > > > not access to internet, they cannot mount > > their directories ! > > > > > I think what he means is that: > > > > client <-> server <-> internet > > > > Client can ping server but if server is not > > connected to internet, > > client can not mount nfs shares from server. > > > client <-> server <-X-> internet > > That is exactly my issue . Excuse me for not being > clear ! Anyway, has somebody a solution . > I have read that client and server must be able to > make a reverse resolution of the client and the > server, but I am not sure of it and I don t have an in > depth knowledge of nfs . > With the internet off, check: ping from client to server by name ping from server to client by name Send us /etc/hosts, /etc/host.conf, /etc/hosts.*, /etc/nsswitch.conf Do you have a firewall that perhaps is changing config depending on internet status? What firewall do you use? Relavent error messages: 1. take a copy of /var/log/syslog on each machine. 2. Try to mount an NFS directory 3. Record any visible error messages on either box 4. Take another copy of /var/log/syslog on each machine and diff with the previous copy, and send the diffs, snipping off extraneous or sensitive data. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
--- Douglas Allan Tutty <[EMAIL PROTECTED]> a écrit : > On Wed, Aug 01, 2007 at 11:00:19AM -0600, Bob Proulx > wrote: > > Stephane Durieux wrote: > > > Of course the network connexion is good ! > > > I can ping the server > > > > But you said that the server cannot access the > network: > > > > > I encounter a problem whith my nfs stations. > If the server has > > > > > not access to internet, they cannot mount > their directories ! > > > > This is a contradiction. You say that the server > cannot connect to > > the internet and you say that you can ping your > server. Please > > explain. > > > > I think what he means is that: > > client <-> server <-> internet > > Client can ping server but if server is not > connected to internet, > client can not mount nfs shares from server. > > Doug. client <-> server <-X-> internet That is exactly my issue . Excuse me for not being clear ! Anyway, has somebody a solution . I have read that client and server must be able to make a reverse resolution of the client and the server, but I am not sure of it and I don t have an in depth knowledge of nfs . Thanks for reply _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
On Wed, Aug 01, 2007 at 11:00:19AM -0600, Bob Proulx wrote: > Stephane Durieux wrote: > > Of course the network connexion is good ! > > I can ping the server > > But you said that the server cannot access the network: > > > > I encounter a problem whith my nfs stations. If the server has > > > > not access to internet, they cannot mount their directories ! > > This is a contradiction. You say that the server cannot connect to > the internet and you say that you can ping your server. Please > explain. > I think what he means is that: client <-> server <-> internet Client can ping server but if server is not connected to internet, client can not mount nfs shares from server. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
Stephane Durieux wrote: > Of course the network connexion is good ! > I can ping the server But you said that the server cannot access the network: > > > I encounter a problem whith my nfs stations. If the server has > > > not access to internet, they cannot mount their directories ! This is a contradiction. You say that the server cannot connect to the internet and you say that you can ping your server. Please explain. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
--- Andrew Sackville-West <[EMAIL PROTECTED]> a écrit : > On Wed, Aug 01, 2007 at 05:51:40PM +0200, Stephane > Durieux wrote: > > Hello > > > > I encounter a problem whith my nfs stations. > > If the server has not access to internet, they > cannot > > mount their directories ! > > in what way is network access broken? > > > > > I have checked /etc/fstab > > nfs server is referenced by is ip > > > > /etc/nsswitch.conf > > files hosts dns nis > > > > /etc/host.conf > > order hosts, bind, nis > > none of these matter if you have no network > connection. If the local > machine cannot access any network then there is no > way to mount nfs > shares. > > what is the output of > > /sbin/ifconfig > > A > Of course the network connexion is good ! I can ping the server _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem while internet access broken
On Wed, Aug 01, 2007 at 05:51:40PM +0200, Stephane Durieux wrote: > Hello > > I encounter a problem whith my nfs stations. > If the server has not access to internet, they cannot > mount their directories ! in what way is network access broken? > > I have checked /etc/fstab > nfs server is referenced by is ip > > /etc/nsswitch.conf > files hosts dns nis > > /etc/host.conf > order hosts, bind, nis none of these matter if you have no network connection. If the local machine cannot access any network then there is no way to mount nfs shares. what is the output of /sbin/ifconfig A signature.asc Description: Digital signature
nfs problem while internet access broken
Hello I encounter a problem whith my nfs stations. If the server has not access to internet, they cannot mount their directories ! I have checked /etc/fstab nfs server is referenced by is ip /etc/nsswitch.conf files hosts dns nis /etc/host.conf order hosts, bind, nis (I would like to know the difference between the two lasts) I ve heard it can be a reverse resolution problem. Can someone explain me it ? What is the file involved in reverse resolution locally ? Thanks for reply _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mounting DVDs via NFS problem
Have fixed the problem as NFS can't export UDF filesystems so mounted the DVD as ISO9660 and it worked. Will keep "exportfs -a" in mind though as sometimes it won't play back the DVD via NFS unless I play about with exportfs a lot. Thanks! Cheers - Piers Darryl Clarke wrote: On 21/01/06, Piers Kittel <[EMAIL PROTECTED]> wrote: Hello all, Am trying to mount a DVD drive via NFS and am having problems. For note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 (hostname - mythtv) is the server. I have this in my /etc/exports: /media/cdrom0 192.168.1.2(ro,sync) and 192.168.1.2 is in the /etc/hosts.allow. If the DVD is not mounted, it works perfectly fine: destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv destiny:/mnt# df Filesystem 1K-blocks Used Available Use% Mounted on mythtv:/media/cdrom0 1829192 1547128184472 90% /mnt/mythtv destiny:/mnt# If I unmount the above, and then mount the DVD on mythtv: mythtv:/home/piers# mount /cdrom mythtv:/home/piers# and try again on destiny, I get: destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv mount: mythtv:/media/cdrom0 failed, reason given by server: Permission denied destiny:/# and in the logs, I get: Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000) Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0) Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted I've googled for a long time with the last message but I can't find any help anywhere. I've tried this on my 2 Macs but had the exact same problem: Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0) Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0) Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted I'm hoping you guys can tell me what I'm doing wrong here? Thanks very much in advance! just a shot in the dark, you might have to 'exportfs -a' after mounting your dvdrom to make the nfs server rehash the directory. -- ~ Darryl ~ [EMAIL PROTECTED] http://smartssa.com / http://darrylclarke.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mounting DVDs via NFS problem
On 21/01/06, Piers Kittel <[EMAIL PROTECTED]> wrote: > Hello all, > > Am trying to mount a DVD drive via NFS and am having problems. For > note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 > (hostname - mythtv) is the server. > > I have this in my /etc/exports: > > /media/cdrom0 192.168.1.2(ro,sync) > > and 192.168.1.2 is in the /etc/hosts.allow. > > If the DVD is not mounted, it works perfectly fine: > > destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv > destiny:/mnt# df > Filesystem 1K-blocks Used Available Use% Mounted on > > mythtv:/media/cdrom0 1829192 1547128184472 90% /mnt/mythtv > destiny:/mnt# > > If I unmount the above, and then mount the DVD on mythtv: > > mythtv:/home/piers# mount /cdrom > mythtv:/home/piers# > > and try again on destiny, I get: > > destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv > mount: mythtv:/media/cdrom0 failed, reason given by server: Permission > denied > destiny:/# > > and in the logs, I get: > > Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) > Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000) > Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from > destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0) > Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted > > I've googled for a long time with the last message but I can't find any > help anywhere. > > I've tried this on my 2 Macs but had the exact same problem: > > Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from > ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0) > Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted > Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from > akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0) > Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted > > I'm hoping you guys can tell me what I'm doing wrong here? > > Thanks very much in advance! just a shot in the dark, you might have to 'exportfs -a' after mounting your dvdrom to make the nfs server rehash the directory. -- ~ Darryl ~ [EMAIL PROTECTED] http://smartssa.com / http://darrylclarke.com
Re: mounting DVDs via NFS problem
On Mon, 23 Jan 2006 11:29:50 + Piers Kittel <[EMAIL PROTECTED]> wrote: > Andrew, > > > how can you mount a dvd over nfs if its not mounted on its local machine? > > Do these numbers above, as they come from destiny match the numbers if they > > are run on mythtv? IOW, are we looking at the same disk here? > > This bit is just to test if I can acutally mount it, i.e. I'm running > the right commands, it all works etc - this confirms the problem > orginates from mounting the DVD itself. The numbers shows the hard > drive sizes, as the cdrom directory is on the hard drive. oh yeah, okay. > > > when you mount /cdrom on mythtv, do the permissions change? what is ls -l > > /cdrom when unmounted and mounted? > > Yup you're correct, and have fixed this problem: > > mythtv:/media# mount /cdrom > mythtv:/media# ls -l > total 2 > lrwxrwxrwx 1 root cdrom 6 2005-06-07 19:30 cdrom -> cdrom0 > dr-xr-xr-x 3 4294967295 4294967295 88 2003-09-08 21:08 cdrom0 > mythtv:/media# > > but if I do the following: > > mythtv:/media# mount -o umask=000,uid=1000,gid=24 /dev/hdc /cdrom > mount: block device /dev/hdc is write-protected, mounting read-only > mythtv:/media# ls -l > total 2 > lrwxrwxrwx 1 root cdrom 6 2005-06-07 19:30 cdrom -> cdrom0 > dr-xr-xr-x 3 piers cdrom 88 2003-09-08 21:08 cdrom0 > mythtv:/media# > > Works nicely, but still have the same problem: > > Jan 23 11:23:13 localhost rpc.mountd: authenticated mount request from > akane.10sca.intranet:956 for /media/cdrom0 (/media/cdrom0) > Jan 23 11:23:13 localhost rpc.mountd: getfh failed: Operation not permitted I have to ask just incase: can you mount other shares? /home/foo for example? A > > Any ideas what I'm doing wrong? > > Thanks very much for your help! > > Regards - Piers > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > pgpaM7TQaRTtl.pgp Description: PGP signature
Re: mounting DVDs via NFS problem
Andrew, how can you mount a dvd over nfs if its not mounted on its local machine? Do these numbers above, as they come from destiny match the numbers if they are run on mythtv? IOW, are we looking at the same disk here? This bit is just to test if I can acutally mount it, i.e. I'm running the right commands, it all works etc - this confirms the problem orginates from mounting the DVD itself. The numbers shows the hard drive sizes, as the cdrom directory is on the hard drive. when you mount /cdrom on mythtv, do the permissions change? what is ls -l /cdrom when unmounted and mounted? Yup you're correct, and have fixed this problem: mythtv:/media# mount /cdrom mythtv:/media# ls -l total 2 lrwxrwxrwx 1 root cdrom 6 2005-06-07 19:30 cdrom -> cdrom0 dr-xr-xr-x 3 4294967295 4294967295 88 2003-09-08 21:08 cdrom0 mythtv:/media# but if I do the following: mythtv:/media# mount -o umask=000,uid=1000,gid=24 /dev/hdc /cdrom mount: block device /dev/hdc is write-protected, mounting read-only mythtv:/media# ls -l total 2 lrwxrwxrwx 1 root cdrom 6 2005-06-07 19:30 cdrom -> cdrom0 dr-xr-xr-x 3 piers cdrom 88 2003-09-08 21:08 cdrom0 mythtv:/media# Works nicely, but still have the same problem: Jan 23 11:23:13 localhost rpc.mountd: authenticated mount request from akane.10sca.intranet:956 for /media/cdrom0 (/media/cdrom0) Jan 23 11:23:13 localhost rpc.mountd: getfh failed: Operation not permitted Any ideas what I'm doing wrong? Thanks very much for your help! Regards - Piers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mounting DVDs via NFS problem
On Sat, 21 Jan 2006 22:04:25 + Piers Kittel <[EMAIL PROTECTED]> wrote: > Hello all, > > Am trying to mount a DVD drive via NFS and am having problems. For > note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 > (hostname - mythtv) is the server. > > I have this in my /etc/exports: > > /media/cdrom0 192.168.1.2(ro,sync) > > and 192.168.1.2 is in the /etc/hosts.allow. > > If the DVD is not mounted, it works perfectly fine: > > destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv > destiny:/mnt# df > Filesystem 1K-blocks Used Available Use% Mounted on > > mythtv:/media/cdrom0 1829192 1547128184472 90% /mnt/mythtv > destiny:/mnt# how can you mount a dvd over nfs if its not mounted on its local machine? Do these numbers above, as they come from destiny match the numbers if they are run on mythtv? IOW, are we looking at the same disk here? > > If I unmount the above, and then mount the DVD on mythtv: > > mythtv:/home/piers# mount /cdrom > mythtv:/home/piers# > > and try again on destiny, I get: > > destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv > mount: mythtv:/media/cdrom0 failed, reason given by server: Permission > denied > destiny:/# when you mount /cdrom on mythtv, do the permissions change? what is ls -l /cdrom when unmounted and mounted? A > > and in the logs, I get: > > Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) > Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000) > Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from > destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0) > Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted > > I've googled for a long time with the last message but I can't find any > help anywhere. > > I've tried this on my 2 Macs but had the exact same problem: > > Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from > ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0) > Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted > Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from > akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0) > Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted > > I'm hoping you guys can tell me what I'm doing wrong here? > > Thanks very much in advance! > > Cheers - Piers > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > pgpkDuxeXYAnI.pgp Description: PGP signature
mounting DVDs via NFS problem
Hello all, Am trying to mount a DVD drive via NFS and am having problems. For note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 (hostname - mythtv) is the server. I have this in my /etc/exports: /media/cdrom0 192.168.1.2(ro,sync) and 192.168.1.2 is in the /etc/hosts.allow. If the DVD is not mounted, it works perfectly fine: destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv destiny:/mnt# df Filesystem 1K-blocks Used Available Use% Mounted on mythtv:/media/cdrom0 1829192 1547128184472 90% /mnt/mythtv destiny:/mnt# If I unmount the above, and then mount the DVD on mythtv: mythtv:/home/piers# mount /cdrom mythtv:/home/piers# and try again on destiny, I get: destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv mount: mythtv:/media/cdrom0 failed, reason given by server: Permission denied destiny:/# and in the logs, I get: Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000) Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0) Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted I've googled for a long time with the last message but I can't find any help anywhere. I've tried this on my 2 Macs but had the exact same problem: Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0) Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0) Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted I'm hoping you guys can tell me what I'm doing wrong here? Thanks very much in advance! Cheers - Piers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem with debian installation
On Mon, 25 Jul 2005, Michael Gass wrote: I am having a problem with a debian install using nfs and a floppy boot. I am trying to install woody (bf2.4 flavor) on an old 486 with 24M ram (Compaq Prolinea 4/66). I am using PLIP as the machine has no network card and no cdrom. <.> "nfs: server 192.168.1.1 not responding, still trying" Sure sounds familiar. What I did was to set up the host as an ftp or http server and all was well, I think the latter easier to do than the former. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NFS problem with debian installation
I am having a problem with a debian install using nfs and a floppy boot. I am trying to install woody (bf2.4 flavor) on an old 486 with 24M ram (Compaq Prolinea 4/66). I am using PLIP as the machine has no network card and no cdrom. This target machine is connected via PLIP to a source machine (686 with 256M ram) running sarge (kernel 2.6). The source machine has a cdrom with the debian install cd. The start of the installation goes fine: boot up with floppies and install driver floppies and the the network. Can ping the two machines. The problem starts with installing the base system - the initial nfs mount works and the target machine reads the file structure on the source machine (I can tell since the the cdrom on the source is running). But after reading in the cd file structure, the installer prompts for the install directory (/instmnt). When I accept the default, nfs dies. dmesg on the target says "nfs: server 192.168.1.1 not responding, still trying" If I try to do "ls" on the target, it just hangs and the only thing that I can do is reboot and start over. Why is nfs dying at this point. I have tried stopping and restarting the nfs-kernel-server on the source machine with no results. Note: The above problem happens with the bf2.4 (2.4 kernel) flavor of woody. I can install the base system just fine with the vanilla (2.2 kernel) flavor of woody. Any ideas? -- Michael Gass Department of Mathematics St. John's University Collegeville, MN 56321-3000 (320) 363-3090 [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
OT: NFS Problem (Text file busy)
I'd put this on a Perl newsgroup, but when I Googled for more info, it came up that this is likely more of an NFS problem. I could not find anything that could actually tell me how to fix it, though. I have a server and a workstation. I'm using Kate (for those who don't use it, it's a KDE text editor with a console visible in the window). I access the files I'm working on in Kate through NFS. In the console, I'm logged into the server through ssh. I've used this setup on other systems (old Mandrake based systems) in the past, but now I'm using it on Debian based systems, so I think the problem is probably a setting I haven't found. When I edit a Perl script in the text editor, and save it (through my NFS share), THEN try to run it through the console logged into the server through ssh, I get this error: bash: /testing/tnet/bin/t-f1: /usr/bin/perl: bad interpreter: Text file busy As best I can find out, this is related to NFS, but I don't recall getting error messages starting with "bash:" before, so I'm wondering if Bash is picking up something I don't know about. If I wait 10-15 seconds, I can run the program. Sometimes it seems to run after a shorter time. Any ideas? Thanks! Hal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bizarre NFS Problem
On Tue, 2004-11-16 at 19:52, Tim Kelley wrote: > Have you looked at tcpdump output while this is happening? you might see some > clues ... I have done a TCP dump and it seems to be just fine, nothing is different from a successful transfer then a failed transfer except at the point it fails. The failure just ends the session and the successful one continues. > If you are using udp, just do > > tcpdump udp or icmp and port nfs > > You might see a lot of icmp error messages, and you'll certainly see the > fragmentation. > > You might try switching to tcp. Most likely udp is the culprit here, since > any sort of network problem at all will result in data loss. Tcp is not > noticeably slower and will work much better. On modern systems tcp and rsize > and wsize of 32k is pretty standard. The above being said, how do I verify that I am using TCP and not UDP? -- o) Derek Wueppelmann (o (D . [EMAIL PROTECTED] D). ((` http://www.monkeynet.ca/ ( ) ` signature.asc Description: This is a digitally signed message part
Re: Bizarre NFS Problem
On Tuesday 16 November 2004 08:45, Derek "The Monkey" Wueppelmann wrote: > I know this is an old thread now, but I finally got a chance to try out > the above. And while I was very hopeful in that it might work it still > ended up with the same results. I don't know about everybody else but I > am thoroughly puzzled by this. Have you looked at tcpdump output while this is happening? you might see some clues ... If you are using udp, just do tcpdump udp or icmp and port nfs You might see a lot of icmp error messages, and you'll certainly see the fragmentation. You might try switching to tcp. Most likely udp is the culprit here, since any sort of network problem at all will result in data loss. Tcp is not noticeably slower and will work much better. On modern systems tcp and rsize and wsize of 32k is pretty standard. -- _ _ _ _ _ _ _ _ _ _ _ _ _ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ ( t | i | m | @ | i | t | . | k | p | t | . | c | c ) \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ GPG key fingerprint = 1DEE CD9B 4808 F608 FBBF DC21 2807 D7D3 09CA 85BF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bizarre NFS Problem
On Fri, 2004-11-05 at 07:14, Ben Hutchings wrote: > Derek "The Monkey" Wueppelmann wrote: > > Hello All, > > > > I'm currently running debian 3.0 r3 and have run into an interesting > > issue with my NFS mounts. On one of my debian systems (I have just done > > an apt-get update/upgrade on all my systems) when copying or creating a > > file on one of the NFS mounted directories I get an input/output error. > > The interesting thing is that this only happens for a file size of > > between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My > > mount point has been setup in fstab with the following options: > > > > rw,auto,soft,rsize=8192,wsize=8192 > > > > Another interesting thing is that if I go to another of my debian > > systems that is running the exact same version of mount and nfs the copy > > works just fine. I am incredibly perplexed as to why this is happening, > > if anybody could shed some light on this that would be great. > > > Perhaps it's something to do with IP fragmentation? That works on > 64-bit (8-byte) units so if there's some kind of bug in fragment > reassembly somewhere along the route then it might well affect fragments > in an 8-byte range of sizes. See if the problem goes away if you reduce > the sizes to 1024, which should prevent fragmentation. (This is bad for > performance so it's not a good solution, but it might help to identify > the source of the problem.) I know this is an old thread now, but I finally got a chance to try out the above. And while I was very hopeful in that it might work it still ended up with the same results. I don't know about everybody else but I am thoroughly puzzled by this. -- o) Derek Wueppelmann (o (D . [EMAIL PROTECTED] D). ((` http://www.monkeynet.ca/ ( ) ` signature.asc Description: This is a digitally signed message part
Re: Bizarre NFS Problem
Derek "The Monkey" Wueppelmann wrote: Hello All, I'm currently running debian 3.0 r3 and have run into an interesting issue with my NFS mounts. On one of my debian systems (I have just done an apt-get update/upgrade on all my systems) when copying or creating a file on one of the NFS mounted directories I get an input/output error. The interesting thing is that this only happens for a file size of between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My mount point has been setup in fstab with the following options: rw,auto,soft,rsize=8192,wsize=8192 Another interesting thing is that if I go to another of my debian systems that is running the exact same version of mount and nfs the copy works just fine. I am incredibly perplexed as to why this is happening, if anybody could shed some light on this that would be great. Perhaps it's something to do with IP fragmentation? That works on 64-bit (8-byte) units so if there's some kind of bug in fragment reassembly somewhere along the route then it might well affect fragments in an 8-byte range of sizes. See if the problem goes away if you reduce the sizes to 1024, which should prevent fragmentation. (This is bad for performance so it's not a good solution, but it might help to identify the source of the problem.) Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bizarre NFS Problem
On Thursday 04 November 2004 02:34, Derek \"The Monkey\" Wueppelmann wrote: > Hello All, > > I'm currently running debian 3.0 r3 and have run into an interesting > issue with my NFS mounts. On one of my debian systems (I have just done > an apt-get update/upgrade on all my systems) when copying or creating a > file on one of the NFS mounted directories I get an input/output error. > The interesting thing is that this only happens for a file size of > between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My > mount point has been setup in fstab with the following options: I know nix about nfs but FWIW, after the just done update/upgrade everything went wierd on my Woody r3 box until I rebooted it. Might be worth a try. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bizarre NFS Problem
Hello All, I'm currently running debian 3.0 r3 and have run into an interesting issue with my NFS mounts. On one of my debian systems (I have just done an apt-get update/upgrade on all my systems) when copying or creating a file on one of the NFS mounted directories I get an input/output error. The interesting thing is that this only happens for a file size of between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My mount point has been setup in fstab with the following options: rw,auto,soft,rsize=8192,wsize=8192 Another interesting thing is that if I go to another of my debian systems that is running the exact same version of mount and nfs the copy works just fine. I am incredibly perplexed as to why this is happening, if anybody could shed some light on this that would be great. Just so everybody knows the command I'm using to create files on the NFS system is: dd if=/dev/urandom of=./test bs=1 count=4833 and it gives me the following error to the console: 4833+0 records in 4833+0 records out dd: closing output file `./test': Input/output error Although creating a file of the appropriate size and copying it would cause the same result. Again just to re-iterate the weirdness is that if I did the above command with a smaller value or a larger value it would work. ie values of 4832, 4841, 8192, etc all work. -- o) Derek Wueppelmann (o (D . [EMAIL PROTECTED] D). ((` http://www.monkeynet.ca/ ( ) ` signature.asc Description: This is a digitally signed message part
More info (Was: NFS problem between Solaris & Debian)
Here is more info: the client reports [EMAIL PROTECTED]>nfsstat -rc Client rpc: Connection oriented: calls badcallsbadxids timeoutsnewcredsbadverfs 6838681 151128 3 297 0 0 timers cantconnnomem interrupts 0 680 0 0 Connectionless: calls badcallsretrans badxids timeoutsnewcreds 293 1 0 0 0 0 badverfstimers nomem cantsend 0 18 0 0 [EMAIL PROTECTED]> timeout >> badxids : packets are never making it to the server. Server too loaded to reply? And the server tells me laurel:/var/local# vmstat 10 procs ---memory-- ---swap-- -io --system-- cpu r b swpd free buff cache si sobibo incs us sy id wa 0 0 5608 5580 31092 298428005688521 0 0 99 0 0 0 5608 5572 31100 29842800 011 12719 0 0 100 0 0 0 5608 5524 31116 29846000 017 16151 0 0 100 0 0 0 5608 5524 31116 29846000 0 0 12417 0 0 100 0 0 0 5608 5524 31116 29846000 0 0 11116 0 0 100 0 0 0 5608 5520 31120 29846000 016 244 208 0 0 100 0 laurel:/var/local# From the id column, server cpu has lots of idle time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NFS problem between Solaris & Debian
NFS problem. Server is a debian Sarge/testing box (kernel 2.4.25-1-386). Client is a solaris 8 box. This afternoon I started to see the following messages in the debian box's /var/log/kern.log: Apr 1 15:40:00 laurel kernel: rpc-srv/tcp: nfsd: sent only -32 bytes of 8324 - shutting down socket What is going on here? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
BTW, is there still a way to mount a windows dirtree via nfs ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Mon, 27 Oct 2003 16:01:06 -0500, Vivek Kumar wrote: > Hi, > > I am trying to mount a directory as nfs filesystem from other machine. I > am getting RPC error on other machine and it says (Host linux box) > is not responding. Though I can ping to the linux box from there and > also I can telnet ot it. > What is that I am missing. Any suggestion. > > Thanks These services are needed to be run on the server side: - NFS server - Portmap Check if one of them is started via Inetd (etc/inetd.conf): if one is then you also need to start inetd. Check the log of your server if it is receiving any requests. Greetings Andre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Monday 27 October 2003 22:01, Vivek Kumar wrote: > I am trying to mount a directory as nfs filesystem from other > machine. I am getting RPC error on other machine and it says > (Host linux box) is not responding. Though I can ping to the linux > box from there and also I can telnet ot it. What ports are open? Perhaps you've firewalled off some of the ports you need. nmap it, perhaps? Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nfs problem
Hi, I am trying to mount a directory as nfs filesystem from other machine. I am getting RPC error on other machine and it says (Host linux box) is not responding. Though I can ping to the linux box from there and also I can telnet ot it. What is that I am missing. Any suggestion. Thanks -- Vivek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
A little more on my nfs problem...
Also, some more stuff I've been noticing: 1) My understanding was that /var/lib/nfs/xtab was the file actually consulted by mountd to respond to an nfs mount request. Interestingly, that file only contains the info on /home, but not on the /shared export, even though /etc/exports includes both. The same directory has a file called etab, and that file does contain both exports. Issuing exportfs -a -v prints out two lines, indicating both exports are being processed, but xtab doesn't change. I don't understand this. exportfs -r gives the same behavoir. I tried exporting another directory (/tmp) by adding it to /etc/exports and reissuing exportfs -a -> the new export got added to etab but not xtab, and in any case I could not mount the new share either - same connection refused error from the workstation. 2) I thought maybe the problem was that the /shared mount point is Reiserfs, thinking (without good reason) that maybe there is a problem with nfs exporting reiser filesystems, but the /tmp export I experimented with is ext2 (as is /home, the export that seems to work, at least for now). I suspect there is something wrong with mountd, and that it died after letting me mount the one export that works, but I cannot figure out what it is. There are no error messages in syslog to help me. nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, Jul 30, 2003 at 06:39:52PM -0500, Ron Johnson wrote: > Thanks. Does sid's 1.0.5-1 work? Yes, seems to be working for me. -- Dave Carrigan Seattle, WA, USA [EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680 UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL Dave is currently listening to Dream Academy - The Edge Of Forever (The Dream Academy) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, 2003-07-30 at 12:08, Dave Carrigan wrote: > On Wed, Jul 30, 2003 at 10:28:29AM -0500, Ron Johnson wrote: > > On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote: > > > > Make sure you're running the most recent ones or else > > > downgrade to 1.0.3-1. > > > # dpkg -l | grep nfs > > ii nfs-common 1.0.3-2 NFS support files common to client and serve > > ii nfs-kernel-ser 1.0.3-2 Kernel NFS server support > ^^^ > > You have to downgrade to 1.0.3-1. Those pesky digits! Thanks. Does sid's 1.0.5-1 work? -- +-+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA | | | | "I'm not a vegetarian because I love animals, I'm a vegetarian | | because I hate vegetables!"| |unknown | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, Jul 30, 2003 at 10:28:29AM -0500, Ron Johnson wrote: > On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote: > > Make sure you're running the most recent ones or else > > downgrade to 1.0.3-1. > # dpkg -l | grep nfs > ii nfs-common 1.0.3-2 NFS support files common to client and serve > ii nfs-kernel-ser 1.0.3-2 Kernel NFS server support ^^^ You have to downgrade to 1.0.3-1. -- Dave Carrigan Seattle, WA, USA [EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680 UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote: > On Wed, Jul 30, 2003 at 12:31:13AM -0400, gerard wrote: > > Everything was working fine with my nfs, rebooted, and now when I try to > > mount an nfs drive this is the error I get "mount: RPC: Unable to > > receive; errno = Connection refused". Any ideas? I havent changed > > anything either, thats why I find it strange. > > There have been some bugs in recent versions of nfs-kernel-server and/or > nfs-common. Make sure you're running the most recent ones or else > downgrade to 1.0.3-1. The same thing has happened to me. On the client: # ps aux |grep portmap daemon 340 0.0 0.0 1316 396 ? SJul29 0:00 /sbin/portmap # ps aux |grep statd root 2477 0.0 0.1 1372 680 ? S10:19 0:00 /sbin/rpc.statd # ps aux |grep lockd root 2462 0.0 0.0 00 ? W 10:19 0:00 [lockd] # dpkg -l | grep nfs ii nfs-common 1.0.3-2 NFS support files common to client and serve ii nfs-kernel-ser 1.0.3-2 Kernel NFS server support # mount /nfs/music mount: RPC: Unable to receive; errno = Connection refused On the server: $ ps aux |grep portmap daemon 272 0.0 0.0 1320 468 ? S Jun25 0:00 [portmap] [EMAIL PROTECTED]:~$ ps aux |grep statd root854 0.0 0.0 1372 680 ? S Jul27 0:00 /sbin/rpc.statd [EMAIL PROTECTED]:~$ ps aux |grep lockd root925 0.0 0.0 00 ? SW Jul27 0:00 [lockd] $ dpkg -l | grep nfs ii nfs-common 1.0.3-2 NFS support files common to client and serve ii nfs-kernel-ser 1.0.3-2 Kernel NFS server support -- +-+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA | | | | "I'm not a vegetarian because I love animals, I'm a vegetarian | | because I hate vegetables!"| |unknown | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, Jul 30, 2003 at 12:31:13AM -0400, gerard wrote: > Everything was working fine with my nfs, rebooted, and now when I try to > mount an nfs drive this is the error I get "mount: RPC: Unable to > receive; errno = Connection refused". Any ideas? I havent changed > anything either, thats why I find it strange. There have been some bugs in recent versions of nfs-kernel-server and/or nfs-common. Make sure you're running the most recent ones or else downgrade to 1.0.3-1. -- Dave Carrigan Seattle, WA, USA [EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680 UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nfs problem
On Wed, 2003-07-30 at 05:31, gerard wrote: > Everything was working fine with my nfs, rebooted, and now when I try to > mount an nfs drive this is the error I get "mount: RPC: Unable to > receive; errno = Connection refused". Any ideas? I havent changed > anything either, thats why I find it strange. try running: /sbin/portmap (needed) /sbin/rpc.statd /sbin/rpc.lockd If you are going to run nfs, then you will need these running, also make sure that /etc/init.d/nfs-common is running on startup. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nfs problem
Everything was working fine with my nfs, rebooted, and now when I try to mount an nfs drive this is the error I get "mount: RPC: Unable to receive; errno = Connection refused". Any ideas? I havent changed anything either, thats why I find it strange. ~gerard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS Problem
Bart Lenoir wrote: Hi, I'm running an NFS server on Red Hat. Connected to the Red Hat I have a Debian which I want to use as an NFS client. Ping, Ftp, Telnet, ... all seems fine. Mount and Umount is working well, however I don't have access to the selected directory. "Permission denied". The only way I can have access to this directory is to set Red Hat /etc/exports to (rw,sync,no_root_squash). Logging in as root on Debian I'm having access but that is not what I want. Why do I get Permission refused as regular user? On another Red Hat I do have access as regular user. rpcinfo -p on Debian # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000241 udp867 status 1000241 tcp870 status 3910021 tcp 32768 sgi_fam 3910022 tcp 32768 sgi_fam 1000211 udp 32769 nlockmgr 1000213 udp 32769 nlockmgr 1000214 udp 32769 nlockmgr Thanks, Bart I think nfs requires u have same user id on both the system if u want to have full rights (very dangerous I think) so u need to change /etc/passwd to have same user id. Redhat starts user id from 500 while Debian starts from 1000, I did manually changed the user id to have nfs access. -- Zhao YouBing, Ph.D student State Key Lab of CAD&CG,Zhejiang University, Hangzhou, 310027, P.R.China Tel : 0571-87951045(O), 87933444(H) Email: [EMAIL PROTECTED] MSN : [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NFS Problem
Hi, I'm running an NFS server on Red Hat. Connected to the Red Hat I have a Debian which I want to use as an NFS client. Ping, Ftp, Telnet, ... all seems fine. Mount and Umount is working well, however I don't have access to the selected directory. "Permission denied". The only way I can have access to this directory is to set Red Hat /etc/exports to (rw,sync,no_root_squash). Logging in as root on Debian I'm having access but that is not what I want. Why do I get Permission refused as regular user? On another Red Hat I do have access as regular user. rpcinfo -p on Debian # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000241 udp867 status 1000241 tcp870 status 3910021 tcp 32768 sgi_fam 3910022 tcp 32768 sgi_fam 1000211 udp 32769 nlockmgr 1000213 udp 32769 nlockmgr 1000214 udp 32769 nlockmgr Thanks, Bart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
--uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 16, 2003 at 06:47:30PM +0100, Piers Kittel wrote: > Furthering the subject... >=20 > Is it possible to get the crontab to email me each time the job=20 > succeeds/fails or is it better to write a shell script and get crontab=20 > to execute the script? Cron usually mails me any errors. I usually end up doing: script &> /dev/null because sometimes it overloads me with mail. Bijan --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/FZx6Uof+95vTyAwRAoaMAJwPVuofSW6i8SmoqmNe2U3r4larKwCdGdBQ j6p5b8On9zZktoDNRx3SJb4= =PmXr -END PGP SIGNATURE- --uAKRQypu60I7Lcqm-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
Furthering the subject... Is it possible to get the crontab to email me each time the job succeeds/fails or is it better to write a shell script and get crontab to execute the script? Cheers - Piers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
Great! Seems to be working
Cheers!
Piers
Michael Heironimus wrote:
> On Wed, Jul 16, 2003 at 01:24:45AM +0100, Piers Kittel wrote:
>
>>Bascially, I've got 2 computers, one which is my main PC (named desire),
>>and the other is a server (named destiny). I'd like the server to
>>backup the /home/piers directory from the main PC. The server is
>>accessing the main PC by NFS and desire:/home is moutned on
>>destiny:/home/desire. I've put in the following line in the crontab
>>file on destiny:
>>
>>00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf
>>/home/desirebackup/home_backup.tar /home/desire/piers
>>
>>but when I tested out the "tar cf /home/desirebackup/home_backup.tar
>>/home/desire/piers" I get a lot of "Permissions denied" errors although
>>some files are read OK. (An example is "tar: /home/desire/piers/.mcoprc:
>>Read error at byte 0, reading 31 byes: Permission denied")
>
>
> It looks like you're using root to run your backup. Normally root is
> remapped to nobody ("root squashing") on NFS mounts for security
> reasons, so root won't have permission to read files that aren't
> world-readable. In the /etc/exports file on the server you can add the
> no_root_squash option to allow root access on an exported filesystem.
> See the man page on exports for details.
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
Florian, You are completely correct, and I totally agree, but the issue here is that the hard drive in Destiny is 12Gb, and the backup is around 6GB and so there isn't room for 2 backups. Interestingly, when I tried to tar the files on the main PC (Desire) and then copy it over via NFS, I always find the receving PC thinks the file is far smaller than it actually is - Destiny thinks the .tar file stored on Desire is 1Gb, but in actuality its 5Gb. Strange. Cheers - Piers Florian Ernst wrote: > Hello Paladin! > > Paladin wrote: > >>On Wed, 16 Jul 2003 11:03:07 +0200 >>Florian Ernst <[EMAIL PROTECTED]> wrote: >> >> >>> Hmm, you completely delete your older backup, and then you try to >>> get a new one? >>> What do you think might happen once an "error" occurs directly >>> after deleting the old backup? You will end up with _no_ backup >>> at all. >>> >>> Better put it in this order: create a new backup, verify its >>> integrity, maybe delete the old backup thereafter. >> >>Why not just do an update on the tar file? > > > That depends on the preferred backup scheme. > > I personally prefer to keep old backups completely untouched / > unchanged in order to eliminate the slightest chance of corruption > during such a change. > Certainly this causes a need for more backup space, but all the time I > have a working backup no matter what happens during the latest > backup. > > Just imagine the tar file gets corrupt during the update, you will end > up with no backup at all. > Imagine the corruption (or simply bad luck) spreads over to the files > you originally wanted to backup, you will end up with _nothing_ at > all. > > I hope to have clarified my point in this, > CU, > Flo > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
Hello Paladin! Paladin wrote: > On Wed, 16 Jul 2003 11:03:07 +0200 > Florian Ernst <[EMAIL PROTECTED]> wrote: > >> Hmm, you completely delete your older backup, and then you try to >> get a new one? >> What do you think might happen once an "error" occurs directly >> after deleting the old backup? You will end up with _no_ backup >> at all. >> >> Better put it in this order: create a new backup, verify its >> integrity, maybe delete the old backup thereafter. > > Why not just do an update on the tar file? That depends on the preferred backup scheme. I personally prefer to keep old backups completely untouched / unchanged in order to eliminate the slightest chance of corruption during such a change. Certainly this causes a need for more backup space, but all the time I have a working backup no matter what happens during the latest backup. Just imagine the tar file gets corrupt during the update, you will end up with no backup at all. Imagine the corruption (or simply bad luck) spreads over to the files you originally wanted to backup, you will end up with _nothing_ at all. I hope to have clarified my point in this, CU, Flo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
On Wed, 16 Jul 2003 11:03:07 +0200 Florian Ernst <[EMAIL PROTECTED]> wrote: > Hmm, you completely delete your older backup, and then you try to > get a new one? > What do you think might happen once an "error" occurs directly > after deleting the old backup? You will end up with _no_ backup > at all. > > Better put it in this order: create a new backup, verify its > integrity, maybe delete the old backup thereafter. Why not just do an update on the tar file? --- Paladin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
Hello Piers! Piers Kittel wrote: > [...Backup...] > 00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf > /home/desirebackup/home_backup.tar /home/desire/piers Hmm, you completely delete your older backup, and then you try to get a new one? What do you think might happen once an "error" occurs directly after deleting the old backup? You will end up with _no_ backup at all. Better put it in this order: create a new backup, verify its integrity, maybe delete the old backup thereafter. CU, Flo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
On Tue, Jul 15, 2003 at 11:02:39PM -0400, MJM wrote:
> On Tuesday 15 July 2003 22:02, Michael Heironimus wrote:
>
> > > but when I tested out the "tar cf /home/desirebackup/home_backup.tar
> > > /home/desire/piers" I get a lot of "Permissions denied" errors although
> > > some files are read OK. (An example is "tar: /home/desire/piers/.mcoprc:
> > > Read error at byte 0, reading 31 byes: Permission denied")
> >
> > It looks like you're using root to run your backup. Normally root is
> > remapped to nobody ("root squashing") on NFS mounts for security
> > reasons, so root won't have permission to read files that aren't
> > world-readable. In the /etc/exports file on the server you can add the
> > no_root_squash option to allow root access on an exported filesystem.
> > See the man page on exports for details.
>
> I logged in as root and tried to write to a directory on an NFS partition
> owned by account1 and got a permission error. Then I did "su account1" and
> was able to write to the partition. Then I did "exit" and was no longer able
> to write the partition. Can the su command be used in the cron script to
> accomplish the tar-up and keep the root-squash in effect?
You could probably do that with su -c, or there may be an option to tell
cron to use an alternate user for that entry (I'm not current on what
Debian's version of cron supports, it's not exactly a typical UNIX
cron). If you're only running a backup of one user account's home
directory you could also put the tar command in that user's crontab
instead of a system-wide one. Or you could run tar through rsh or ssh.
--
Michael Heironimus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
On Tuesday 15 July 2003 22:02, Michael Heironimus wrote:
> > but when I tested out the "tar cf /home/desirebackup/home_backup.tar
> > /home/desire/piers" I get a lot of "Permissions denied" errors although
> > some files are read OK. (An example is "tar: /home/desire/piers/.mcoprc:
> > Read error at byte 0, reading 31 byes: Permission denied")
>
> It looks like you're using root to run your backup. Normally root is
> remapped to nobody ("root squashing") on NFS mounts for security
> reasons, so root won't have permission to read files that aren't
> world-readable. In the /etc/exports file on the server you can add the
> no_root_squash option to allow root access on an exported filesystem.
> See the man page on exports for details.
I logged in as root and tried to write to a directory on an NFS partition
owned by account1 and got a permission error. Then I did "su account1" and
was able to write to the partition. Then I did "exit" and was no longer able
to write the partition. Can the su command be used in the cron script to
accomplish the tar-up and keep the root-squash in effect?
--
Mike Mueller
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tar/NFS problem
On Wed, Jul 16, 2003 at 01:24:45AM +0100, Piers Kittel wrote:
> Bascially, I've got 2 computers, one which is my main PC (named desire),
> and the other is a server (named destiny). I'd like the server to
> backup the /home/piers directory from the main PC. The server is
> accessing the main PC by NFS and desire:/home is moutned on
> destiny:/home/desire. I've put in the following line in the crontab
> file on destiny:
>
> 00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf
> /home/desirebackup/home_backup.tar /home/desire/piers
>
> but when I tested out the "tar cf /home/desirebackup/home_backup.tar
> /home/desire/piers" I get a lot of "Permissions denied" errors although
> some files are read OK. (An example is "tar: /home/desire/piers/.mcoprc:
> Read error at byte 0, reading 31 byes: Permission denied")
It looks like you're using root to run your backup. Normally root is
remapped to nobody ("root squashing") on NFS mounts for security
reasons, so root won't have permission to read files that aren't
world-readable. In the /etc/exports file on the server you can add the
no_root_squash option to allow root access on an exported filesystem.
See the man page on exports for details.
--
Michael Heironimus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tar/NFS problem
Hello Bascially, I've got 2 computers, one which is my main PC (named desire), and the other is a server (named destiny). I'd like the server to backup the /home/piers directory from the main PC. The server is accessing the main PC by NFS and desire:/home is moutned on destiny:/home/desire. I've put in the following line in the crontab file on destiny: 00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf /home/desirebackup/home_backup.tar /home/desire/piers but when I tested out the "tar cf /home/desirebackup/home_backup.tar /home/desire/piers" I get a lot of "Permissions denied" errors although some files are read OK. (An example is "tar: /home/desire/piers/.mcoprc: Read error at byte 0, reading 31 byes: Permission denied") Any ideas? Cheers - Piers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NFS: Problem in changing runlevels
Hello! I have installed Debian Linux 3.0r1 and a home-compiled 2.4.18 kernel (no additional patches) with NFS-kernel-server (compiled in). Everything seems to work, but when I change the runlevel to 1 and to 2 after doing something or simply typing CNTRL-D the system hangs at this point: Starting NFS kernel daemon: nfsd I can recover by pressing CNTRL-ALT-DEL and it shuts down and reboots normally. When I look into /var/log/daemon.log, I find these lines (tail part): Jun 15 16:38:38 fserverII init: Switching to runlevel: 1 Jun 15 16:38:45 fserverII rpc.statd[149]: Caught signal 15, un-registering and exiting. Jun 15 16:39:23 fserverII rpc.statd[250]: Version 1.0 Starting Jun 15 16:39:23 fserverII rpc.statd[251]: unable to register (statd, 1, udp). Jun 15 16:39:59 fserverII init: Switching to runlevel: 6 Jun 15 16:40:54 fserverII rpc.statd[148]: Version 1.0 Starting BTW: I _have_ the looback device configured (as done by the debian-setup). I mentioned this, because somebody else seemed to have troubles with NFS without it. Does anyone know went wrong? Tanks. __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NFS problem
> > when I check to status of nfs on the server I';m trying > to > > setup, the rpcinfo -p command returns > > > > rpcinfo: can't contact portmapper RPC: remote system > error > > - connection refused > > > > the lsmod command shows nfsd, nfs and lockd. what did > I do > > wrong? what am I overlooking. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem
On Fri, 8 Mar 2002 09:52:20 -0600 Dimitri Maziuk <[EMAIL PROTECTED]> wrote: > * Axel Boyrie ([EMAIL PROTECTED]) spake thusly: > > Hi, > > > > I am using Woody. I mount NFS directory from Solaris 2.8 where files are > > owed by nobody.nobody > > > > once NFS mounted on Woody, with the kernel 2.2.20 files appear as own by > > nobody.nogroup > > > > But with kernel 2.4.17 files appear with a uid and gid number 4294967294 > > !!??? > > > > i've try to change the NFS protocole version with nfsvers=2 in fstab but it > > does nothing > > > > Is kernel 2.4 needs special configuration for NFS ? > > Nope. No problems NFS-mounting stuff off Solaris 8 here. Check your kernel > compile options. Mine is compiled with CONFIG_NFS_FS=y, CONFIG_NFS_V3=y > (it's a home-made kernel, not .deb). I use kernel-image-2.4.17-686.deb, it is compiled with CONFIG_NFS_FS=m, CONFIG_NFS_V3=y > > Dima > -- > We're sysadmins. Sanity happens to other people. -- Chris > King > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NFS problem
* Axel Boyrie ([EMAIL PROTECTED]) spake thusly: > Hi, > > I am using Woody. I mount NFS directory from Solaris 2.8 where files are owed > by nobody.nobody > > once NFS mounted on Woody, with the kernel 2.2.20 files appear as own by > nobody.nogroup > > But with kernel 2.4.17 files appear with a uid and gid number 4294967294 !!??? > > i've try to change the NFS protocole version with nfsvers=2 in fstab but it > does nothing > > Is kernel 2.4 needs special configuration for NFS ? Nope. No problems NFS-mounting stuff off Solaris 8 here. Check your kernel compile options. Mine is compiled with CONFIG_NFS_FS=y, CONFIG_NFS_V3=y (it's a home-made kernel, not .deb). Dima -- We're sysadmins. Sanity happens to other people. -- Chris King
NFS problem
Hi, I am using Woody. I mount NFS directory from Solaris 2.8 where files are owed by nobody.nobody once NFS mounted on Woody, with the kernel 2.2.20 files appear as own by nobody.nogroup But with kernel 2.4.17 files appear with a uid and gid number 4294967294 !!??? i've try to change the NFS protocole version with nfsvers=2 in fstab but it does nothing Is kernel 2.4 needs special configuration for NFS ? Axel
Re: puzzling NFS problem
On Thu, Feb 07, 2002 at 11:25:07PM +, Jonathan Matthews wrote:
[...]
> A workaround for this was to increase the number of nfsd instances on
> the server, set in one of the nfs scripts in /etc/init.d. I can't
> remember what the line was, and I haven't got nfs installed anymore, but
> look for something like INSTANCES=8 near the top of
> /etc/init.d/{nfs-server,nfs,nfs-common}. If you've never played with
> it, it'll be set to the default (8). Increase this either until your
> box blows, or the symptoms go away - your choice.
Jonathan: thans for your reply! I found a line 'RPCNFSDCOUNT=8' in
/etc/init.d/nfs-kernel-server and bumped it up to 32. So far so good
--
Henry House
The attached file is a digital signature. See
for information. My OpenPGP key: .
pgpTbtaF4Yhaf.pgp
Description: PGP signature
Re: puzzling NFS problem
On Thu, Feb 07, 2002 at 02:54:03PM -0800, Henry House wrote:
> In the last few days, I've had an intermittent problem with a mail server
> that has /home mounted over NFS and delivers mail directly to user's
> directories. The following message appears over and over in the kernel log:
> Feb 7 14:45:14 romana kernel: lockd: task 168650 can't get a
request slot
[snip]
> [restarted nfs-common on romana and wotan, the nfs server]
> Feb 7 14:45:17 romana kernel: kmod: runaway modprobe loop assumed and
> stopped
> romana:~# Feb 7 14:45:17 romana last message repeated 4 times
> [all seems to be well now, no more log messages]
>
> In the place marked above, I have restarted nfs-common, which seems to cure
> the problem until it comes back. While lockd is complaining, the process
> table shows many instanced of exim in state 'D' (uninterruptible sleep,
> usually do to IO: obviously because of the NFS problem). While the trouble is
> occurring, the files in the NSF mounts still seem to be accessible to shell
> commands (unless the system has not run out of file descriptors).
>
> On Romana the NFS client drivers are modules.
Hi Henry - I had this a while ago.
It happened for me while I was fpt'ing large files from a windows box
to a linux one, and the directory I was copying /to/ was NFS mounted
from another linux box. The problem seemed to be that, due to the
inherent slowness in NFS file transfers, the available resources
of the NFS box that served the mount were requested, one after
another, faster than each finished. The write requests caught up with
the nfs server's capability to read them.
A workaround for this was to increase the number of nfsd instances on
the server, set in one of the nfs scripts in /etc/init.d. I can't
remember what the line was, and I haven't got nfs installed anymore, but
look for something like INSTANCES=8 near the top of
/etc/init.d/{nfs-server,nfs,nfs-common}. If you've never played with
it, it'll be set to the default (8). Increase this either until your
box blows, or the symptoms go away - your choice.
HTH,
jc
--
When you and friend disturb a bear, try to remember that, while running
away, it's not the /bear/ you have to outrun
puzzling NFS problem
In the last few days, I've had an intermittent problem with a mail server that has /home mounted over NFS and delivers mail directly to user's directories. The following message appears over and over in the kernel log: Feb 7 14:45:11 romana kernel: lockd: task 172507 can't get a request slot Feb 7 14:45:11 romana kernel: lockd: task 173492 can't get a request slot Feb 7 14:45:11 romana kernel: lockd: task 165077 can't get a request slot Feb 7 14:45:11 romana kernel: lockd: task 163791 can't get a request slot Feb 7 14:45:12 romana kernel: lockd: task 158725 can't get a request slot Feb 7 14:45:12 romana kernel: lockd: task 167382 can't get a request slot Feb 7 14:45:13 romana kernel: lockd: task 170975 can't get a request slot Feb 7 14:45:14 romana kernel: lockd: task 164987 can't get a request slot Feb 7 14:45:14 romana kernel: lockd: task 168650 can't get a request slot [restarted nfs-common on romana and wotan, the nfs server] Feb 7 14:45:17 romana kernel: kmod: runaway modprobe loop assumed and stopped romana:~# Feb 7 14:45:17 romana last message repeated 4 times [all seems to be well now, no more log messages] In the place marked above, I have restarted nfs-common, which seems to cure the problem until it comes back. While lockd is complaining, the process table shows many instanced of exim in state 'D' (uninterruptible sleep, usually do to IO: obviously because of the NFS problem). While the trouble is occurring, the files in the NSF mounts still seem to be accessible to shell commands (unless the system has not run out of file descriptors). On Romana the NFS client drivers are modules. -- Henry House The attached file is a digital signature. See <http://romana.hajhouse.org/pgp> for information. My OpenPGP key: <http://romana.hajhouse.org/hajhouse.asc>. pgppoxBeCL44k.pgp Description: PGP signature
NFS problem
Hello *, I am having permissions problems with a NFS mount that I just can't figure out and I'm hoping someone can help. I am NFS mounting a USB floppy drive on machine A by using automount on machine B. The floppy shows it is mounted rwxrwxrwx and owned root.root. Any user can read and write to the disk (as I want) but only root can create a new file. I need to give other users the ability to write to the floppy disk. I am exporting the drive (rw,no_root_squash) and automounting it -fstype=nfs,retry=1,soft Any suggestions why a normal user can not create a file and how to let them? Pete -- http://www.elbnet.com ELB Internet Service, Inc. Web Design, Computer Consulting, Internet Hosting
Re: NFS problem
Nicolas Lamirault said: > hi debian users > somebody have an idea to correct me in my config ? > thanks sounds like a permissions issue. what userid are you trying to view the files as? either make sure that that userid(the numerical id) has access to those files or turn on the no_root_squash option in /etc/exports on the server and view the files as root. if that doesn't work try posting again.. nate
NFS problem
hi debian users i have a problem with NFS : i have the domaine 'foo' on B,C and D computer i would like to export a repertory to all the domain. So on each /etc/exports file i write : for B : /share *.foo for C : /usr/local/share*.foo for D : /home/divers*.foo i want to mount this repertory on the A computer. So on /etc/fstab : B:/share/mnt/A nfs rsize=8192,wsize=8192,soft 0 0 C:/usr/loca/share /mnt/B nfs rsize=8192,wsize=8192,soft 0 0 D:/home/divers /mnt/C nfs rsize=8192,wsize=8192,soft 0 0 and for export the repertory /mnt to all the domain, i write on /etc/export on A computer : /mnt*.foo on computer B, i write this in /etc/fstab : A:/mnt /mnt/A nfs rsize=8192,wsize=8192,soft 0 0 so in /mnt/A, i see repertory B,C, and D, if i go to B, i have also some repertory, but they are all empty ! why ?? somebody have an idea to correct me in my config ? thanks -- Nicolas Lamirault CVF Bordeaux 22 quai de Bacalan 33000 BORDEAUX
Re: 2.4.6 NFS problem
On Wed, 24 Oct 2001, Miquel van Smoorenburg wrote: > > You're not running 'portmap' on the client or /etc/hosts.allow > prevents access to it. Fix that. oh man . . . thanks. -- ) ,_),_) (-(__ |_ _ _ |/ ) | |(_)(_ |\ ( \_, ___ | http://www.exitwound.org : hard to find | ___ | After a number of decimal places, nobody | | gives a damn. | ___ -BEGIN GEEK CODE BLOCK- | Version: 3.1 | | GJ/IT d- s: a C+++>$ UL P+++ L+++ E--- W++| | N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ | | R tv+@ b+ DI D+ G++ e h r+++ y+++ | --END GEEK CODE BLOCK--
Re: 2.4.6 NFS problem
In article <[EMAIL PROTECTED]>, Stephen E. Hargrove <[EMAIL PROTECTED]> wrote: >On the 2.2.18 kernel, mount /swlf works perfectly. I recently upgraded >the kernal to 2.4.6, and now all of my mounts time out. The following >appears in my /var/log/messages: > >Oct 24 09:10:17 calypso kernel: portmap: server localhost not responding, >timed out You're not running 'portmap' on the client or /etc/hosts.allow prevents access to it. Fix that. Alternatively mounting with the "nolock" option might help. The userlevel NFS server doesn't support it anyway. Mike. -- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" -- Albert Einstein.
2.4.6 NFS problem
i'm running a RedHat 6.1 box with kernel 2.2.17 with the following: # rpc.mountd --version Universal NFS Server 2.2beta37 # rpc.nfsd --version Universal NFS Server 2.2beta37 # cat /etc/exports /usr/office/clients 192.168.2.2/255.255.255.0(rw) 192.168.2.6/255.255.255.0(rw) /usr/office/closed 192.168.2.2/255.255.255.0(rw) 192.168.2.6/255.255.255.0(rw) /usr/office/forms 192.168.2.2/255.255.255.0(rw) 192.168.2.6/255.255.255.0(rw) /swlf 192.168.2.2/255.255.255.0(rw) 192.168.2.6/255.255.255.0(rw) I have a machine that was running Debian Woody with kernel 2.2.18 which needs access to the RedHat box. I have the following set up: # mount --version mount: mount-2.11h # cat /etc/fstab | grep rsize pappy:/usr/office/clients /mnt/clients/open nfs rsize=8192,wsize=8192,noauto,user 0 0 pappy:/usr/office/closed /mnt/clients/closed nfs rsize=8192,wsize=8192,noauto,user 0 0 pappy:/usr/office/forms/forms nfs rsize=8192,wsize=8192,noauto,user 0 0 pappy:/swlf /swlf nfs rsize=8192,wsize=8192,noauto,user 0 0 On the 2.2.18 kernel, mount /swlf works perfectly. I recently upgraded the kernal to 2.4.6, and now all of my mounts time out. The following appears in my /var/log/messages: Oct 24 09:10:17 calypso kernel: portmap: server localhost not responding, timed out Oct 24 09:11:57 calypso kernel: portmap: server localhost not responding, timed out Oct 24 09:11:57 calypso kernel: lockd_up: makesock failed, error=-5 Oct 24 09:13:37 calypso kernel: portmap: server localhost not responding, timed out Can anyone help out? I'm stuck and have no idea where to look. -- ) ,_),_) (-(__ |_ _ _ |/ ) | |(_)(_ |\ ( \_, ___ | http://www.exitwound.org : hard to find | ___ | Marriage is a three ring circus: engagement | | ring, wedding ring, and suffering. -- Roger | | Price | ___ -BEGIN GEEK CODE BLOCK- | Version: 3.1 | | GJ/IT d- s: a C+++>$ UL P+++ L+++ E--- W++| | N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ | | R tv+@ b+ DI D+ G++ e h r+++ y+++ | --END GEEK CODE BLOCK--
Re: Weird NFS Problem: Input/Output Errors, etc.
On 14 Aug 2001 18:59:23 +0200, Bjoern Buerger wrote: > Am Mon, 13 Aug 2001 schrieb Michael Heldebrant: > > > > > What file system is the nfs exports running on? I seem to recall some > > > > discussion of reiserfs and nfs problems. > > > > > > They are running on ext2 file systems, > > > placed on two RAID5 arrays. > > Thats odd. Do backups and fsck run cleanly from the server on the raid > > array? > > Yes, they do. I just checked the actual backup tape - everything ok. > fsck says, all filesystems of the server are clean. Is there any way to take the files that have given errors, put them on a non-raid nfs exported drive and test access again to see if it's specific to raid and NFS? Have you gotten in touch with the kernel mailing list on this yet? They may have some deeper insight. --mike
Re: Weird NFS Problem: Input/Output Errors, etc.
Am Mon, 13 Aug 2001 schrieb Michael Heldebrant: > > > What file system is the nfs exports running on? I seem to recall some > > > discussion of reiserfs and nfs problems. > > > > They are running on ext2 file systems, > > placed on two RAID5 arrays. > Thats odd. Do backups and fsck run cleanly from the server on the raid > array? Yes, they do. I just checked the actual backup tape - everything ok. fsck says, all filesystems of the server are clean. I´ve no idea, what´s causing these problems. Ciao, Bjørn -- o_) Bjoern Buergerhttp://bbuerger.home.pages.de .-. _/\ .--- --/---\-/(/-' Studentenwohnheim Langer Kamp LUG-Braunschweig `-'http://www.lk.etc.tu-bs.de http://www.lug-bs.de
Re: Weird NFS Problem: Input/Output Errors, etc.
Am Mon, 13 Aug 2001 schrieb Michael Heldebrant: > > Server: > > --- > > Debian unstable > > Kernel 2.4.6 > > nfs-common: 1:0.3.1-1 > > nfs-user-server:2.2beta47-10 > > > > Clients: > > > > Debian unstable > > Kernel 2.4.6 > > nfs-common: 1:0.3.2-2 > > > What file system is the nfs exports running on? I seem to recall some > discussion of reiserfs and nfs problems. They are running on ext2 file systems, placed on two RAID5 arrays. Ciao, Bjørn -- o_) Bjoern Buergerhttp://bbuerger.home.pages.de .-. _/\ .--- --/---\-/(/-' Studentenwohnheim Langer Kamp LUG-Braunschweig `-'http://www.lk.etc.tu-bs.de http://www.lug-bs.de
Re: Weird NFS Problem: Input/Output Errors, etc.
On 12 Aug 2001 17:03:23 +0200, Bjoern Buerger wrote: > > Since last week I've had some really weird problems with NFS, > but I do not know where do search for the problem. Maybe some > of you have com across somethink like the following: <-snip-> > > Server: > --- > Debian unstable > Kernel 2.4.6 > nfs-common: 1:0.3.1-1 > nfs-user-server:2.2beta47-10 > > Clients: > > Debian unstable > Kernel 2.4.6 > nfs-common: 1:0.3.2-2 > What file system is the nfs exports running on? I seem to recall some discussion of reiserfs and nfs problems. --mike
Weird NFS Problem: Input/Output Errors, etc.
Since last week I've had some really weird problems with NFS, but I do not know where do search for the problem. Maybe some of you have com across somethink like the following: The problems occur on three NFS Clients (two of them diskless) while the Server shows no problems with the same files. Even the Servers Logfiles are clean ... After rebooting the Client, the Files are accessible again, but other file accesses fail. Apt and dpkg fail during each ~ 3rd installation, showing errors like "Input/output error" or dpkg: error processing /var/cache/apt/archives/slang1_1.4.4-3.1_i386.deb (--unpack): unable to create `./lib/libslang.so.1.4.4': Too many levels of symbolic links while logging to the client's sylog: Aug 12 17:01:54 hobbes kernel: nfs_refresh_inode: inode 1097449706 mode changed, 0120777 to 010 Another Example: [EMAIL PROTECTED]:~$ ls -l /usr/share/man/man1/ ls: /usr/share/man/man1/gvim.1.gz: Input/output error ls: /usr/share/man/man1/gvim.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/gview.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/rgvim.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/rgview.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/ex.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/rvim.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/rview.1.gz.dpkg-tmp: Input/output error ls: /usr/share/man/man1/view.1.gz.dpkg-tmp: Input/output error total 5720 -rw-r--r--1 root root 534 Jul 5 23:31 822-date.1.gz [...] At the same time, the following errors were logged: Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353261 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353262 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353263 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353264 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353275 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353276 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353277 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353288 mode changed, 0100644 to 0120777 Aug 12 16:36:27 hobbes kernel: nfs_refresh_inode: inode 1094353659 mode changed, 0100644 to 0120777 Any Ideas ? Server: --- Debian unstable Kernel 2.4.6 nfs-common: 1:0.3.1-1 nfs-user-server:2.2beta47-10 Clients: Debian unstable Kernel 2.4.6 nfs-common: 1:0.3.2-2 Ciao, Bjørn -- o_) Bjoern Buergerhttp://bbuerger.home.pages.de .-. _/\ .--- --/---\-/(/-' Studentenwohnheim Langer Kamp LUG-Braunschweig `-'http://www.lk.etc.tu-bs.de http://www.lug-bs.de
nfs problem
Hi, I've got a Debian 2.2 working as a nis server for a Mandrake 7.2 client. I've installed nfs-kernel-server on the debian and configured /etc/exports to export /home/nis (the nis users) to everybody but the Mandrake client isn't able to mount the directory (the nis login works). I've got a "Connection Refused" message on the Mandrake; If I list the messages log file on the server, it tells me that a connection has been refused because the wanted directory was not exported... Here is my export file: /etc/exports: /home/nis(rw,root_squash) If I type exportfs, it answer me that /home/nis is exported to rpc.mountd and rpc.nfsd are working. The only thing I don't understand in the server configuration is that when I'm typing exportfs -r, the /var/lib/yp/etab is filled properly but the /var/lib/yp/xtab is empty... Can anyone help me ? Thanks in advance, nomad
Re: nfs-problem
On Thu, May 31, 2001 at 03:05:44PM +0200, Alexander Gun uttered: > May 31 15:01:38 asterix kernel: nsm_mon_unmon: rpc failed, status=-13 > May 31 15:01:38 asterix kernel: lockd: cannot monitor 192.168.13.100 > May 31 15:01:38 asterix kernel: lockd: failed to monitor 192.168.13.100 > Make sure nfs-common is installed on both machines. -- Steve "I'm a sysadmin because I couldn't beat a blind monkey in a coding contest." --Me
