NFS Disconnected

We have a Solaris 10 server that shares by NFS a directory.
On the Mac side, we mount (nosuid, nodev, rdirplus) this directory as home directory for some users.
In the kernel.log file we have the following messages :
Jan 19 15:57:51 Mac-Pro-de-xxxx kernel[0]: nfs server 10.10.7.2:/DATA/PROFIL/home_dir: lockd not responding
Jan 19 15:58:07 Mac-Pro-de-xxxx kernel[0]: nfs server 10.10.7.2:/DATA/PROFIL/home_dir: lockd alive again
Jan 19 15:58:21 Mac-Pro-de-xxxx kernel[0]: nfs server 10.10.7.2:/DATA/PROFIL/home_dir: lockd not responding
Jan 19 15:58:32 Mac-Pro-de-xxxx kernel[0]: nfs server 10.10.7.2:/DATA/PROFIL/home_dir: lockd alive again
Jan 19 15:58:46 Mac-Pro-de-xxxx kernel[0]: nfs server 10.10.7.2:/DATA/PROFIL/home_dir: lockd not responding
The mac displays a box with a message that says 'Connexion interrompue' (lost connexion). But when we did a 'ls -al' in a terminal all looks fine.
On the solaris server side there's no messages even in debug mode.
Any ideas ?

I am also experiencing this problem. Running the newer Oracle Solaris 11 Express and Snow Leopard as clients.
Doing a rsync of a home directory looks like this...
Desktop/Personal/Internet Usage/
Desktop/Personal/Internet Usage/1395696624.png
Desktop/Personal/Internet Usage/._1395696624.png
Desktop/Personal/Internet Usage/1395699028.png
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd not responding
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd alive again
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd not responding
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd alive again
Desktop/Personal/Internet Usage/._1395699028.png
Desktop/Personal/Internet Usage/Screen shot 2011-08-09 at 3.17.03 PM.png
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd not responding
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd alive again
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd not responding
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd alive again
Desktop/Personal/Internet Usage/._Screen shot 2011-08-09 at 3.17.03 PM.png
Desktop/Personal/Internet Usage/Screen shot 2011-08-11 at 1.38.09 PM.png
nfs server 10.23.0.5:/tank/users/mathieu/backups: lockd not responding
Connection seems to hang but then comes back. so it works anyway, it seems, but it is probably much slower than it could be. hard to tell, at this point.
I think I will try if I can disable the ._* temp files

Similar Messages

NFS Problems - Disconnects in iTunes

I think I have this problem posted by scree and I want to look at the posted solution buy the solution link is dead, the original thread is archived and I don't know how to send a message to scree.
Anyone know the solution described at http://blog.lemon23.com/news/nfs-unter-leopard/nfs-unter-leopard.html ?
scree
Posts: 2
From: Austria
Registered: Nov 18, 2007
Re: NFS problems, file locking???
Posted: Nov 18, 2007 12:03 PM in response to: jt519
i expirienced the same problems (and even more) with my ubuntu-NFS-server and my mac (as a client) which worked very good in 10.4. no problems on the terminal, but lots of disconnects and interrupted server connections when using itunes or iphoto via NFS...
Macbook 13.3 Core Duo Mac OS X (10.5.1)
scree
Posts: 2
From: Austria
Registered: Nov 18, 2007
I GOT IT!
Posted: Nov 19, 2007 12:24 PM in response to: scree
Solved
solution posted here: http://blog.lemon23.com/news/nfs-unter-leopard/nfs-unter-leopard.html
no more interrupts, everything is working fine.

I found your post while digging for answers to the same problem myself. Essentially, my NFS mount of my iTunes library (Centos 5.1 server, gigabit ethernet) was working fine until I hooked up my 40GB iPod (no problem with the smaller ones). I would get the same NFS disconnects that I had with iPhoto, which had made it impossible to use the NFS mount for it.
Well, the good news is that I found a copy of the post you had a link for in the internet archive: http://web.archive.org/web/20080212115443/http://blog.lemon23.com/news/nfs-unter -leopard/nfs-unter-leopard.html . Essentially, the author suggests 3 things:
1) use the same uid and gid for users on your Mac and NFS server
2) disable the generation of the hidden OS X files (e.g. .DSStore) by using 'defaults write com.apple.desktopservices DSDontWriteNetworkStores true'
3) change the NFS mount options to 'locallocks rsize=32768 wsize=32768 intr noatime'
I knew that 1) was important and already had that in place. 2) I don't think should make a difference, it didn't do the trick for the OP either. 3) essentially tells NFS to use local locks, to set the local read and write size to 32k bytes (could have used rwsize=32768 instead) and to allow for any NFS operations to be interrupted. I am not sure that the noatime option is supported in OS X, but on linux machines it tells the client to not constantly update atime on NFS files.
Digging finally into my system.log, I find lots of errors from lockd (lockd not responding), so my hunch is that the most important setting was the 'locallocks' option for mount_nfs (via the Directory Utility app). In any case, my disconnects (doing all 3 of the above) have vanished, even for iPhoto although I have only tested that very briefly.
Hope this helps!

AFP Shares

Hi. I am experiencing a lot of problems with MAC OSX mountain lion and network shares, maybe someone here can help me.
I have a freenas installed where I keep all my multimedia files (i.w. photos, musics, etc...) and I have 2 users on Mac that I normally fastswitch between then (my wife and mine!).
Problem is, I only could manage to give read and write permissions for bouth user over the same mount using NFS, but when I use NFS I got a lot of disconnections when using a lot of load (like browsing pictures).
I was wondering if is any way I could mount a AFP share and bouth users on make could read and write all files (even the new created ones)?
Any help or comments on the matter will be appreciated.
Thanks, Allan

The NFS disconnections should be related to the NAS itself. But I would like to share a mount with AFP to all my logged users. if this is possible it will be really nice.
Thanks, Allan

The Plague of the Disconnecting Xsan

I am living in Xsan H.e.l.l. I pray someone can save me from this torture.
Anyways, here is the situation:
I've been working on trying to make an xsan work for over 6 months now. The latest problem is I am getting constant disconnects when accessing large amounts of small files on the xsan. This is reproducable consistently. I get an error that says "Server connection interrupted: volumename". My only option is to "Disconnect".
I have three Xservers running 10.4.6. I have one brand new Xraid box. I'm running Xsan 1.2.
I have one client xserver
and two controller xservers, with one high priority and one medium priority.
I've done the following:
(1) Tried the manual configuration mentioned on Apple's web site article number 302135
This resulted in the qlogic switch placing all of my xserves as "targets" when they are actually initiators. An it makes my xraid box be "Unknown". This doesn't help stop the disconnects. So I put it back on Auto I/O stream and Auto Device scan and the devices are properly labelled as initiators and targets.
(2) I called up Qlogic and talked to them, they said that this problem normally happens with lots of small files. Their answer to the problem was to go into the Apple Fibre Utility on all of the systems and change the settings so that the Fibre ports run at 1gb/s and it is set up as point-to-point. Which I did. No effect.
(3) I had a gigabit layer 3 switch that I had been using for the private network for the Xsan's meta data. At an apple tech's suggestion, I installed a 10/100 hub instead, but this doesn't affect the disconnects either.
I'm at a loss and my boss is coming back on monday and I still have a unusuable Xsan. Can anyone help me?
I've talked to Apple Enterprise Techs, but they like to just blaim this on the Qlogic switch without ever trying to understand what is going on.
Thank you
David
Mac OS X (10.4.6)
Mac OS X (10.4.6)

I'm having the same problem, only I'm mounting a Sun system running solaris. I simply try to do an ls on a directory containing perhaps a hundred or two text files and it just hangs. I can't control-c the process and am forced to control-z/kill -9. I then start seeing nfs errors like this:
nfs server dyeset:/users: not responding
nfs server dyeset:/users: not responding
nfs server dyeset:/users: not responding
nfs server dyeset:/users: not responding
nfs server dyeset:/users: not responding
nfs server dyeset:/users: not responding
Smaller directories work just fine and I don't get the errors until I try to do something in a large directory. Then I eventually get the window the original poster described "Server connection interrupted: volume-name" and disconnect is the only option. I can re-establish the mount with:
sudo kill -HUP `cat /var/run/automount.pid`
but I consistently cannot do anything in large directories. I was looking at the man page for mount_nfs. Perhaps the -r option would alleviate the problem? The only option I have set in niutil for the mount is "-P". I've used similar mounts in the past without -P on 10.3.9 and never had this problem. That was a sun/solaris system as well, albeit a different system.
Any suggestions?
Thanks,
Rob
G4 Mac OS X (10.4.6)

Server for NFS deletes the partially copied file after failover

Hello,
I found the strange behaviour in Server for NFS in the microsoft foc cluster.
I have a foc cluster of two nodes(windows server 2k12r2) and server for nfs role is installed on both. now I did mount the export from the client(windows server 2k12r2) where client for nfs role is installed;
and a large file copying from the clients local drive to the mounted export is started.
Now during this copying operation I did switch the export to second node(moved it using the failover cluster manager wizard). and what I found is the copying interrupts with
error message "there is problem accessing file path" and on retry the copying starts all over again, I mean if the 50% was copied previously then
after retry it will start from 0%.
I watched the system events on second node with the "procmon" and I found; after the disk gets attached to the second node, the delete operation is get called for this file.
Now what I need to know is why this delete is been called and who made this called. In the stack of the delete operation I could track the nfssvr.sys but not sure what attributes of that file made it to call the
delete.

Hi,
It takes us some time to create a failover cluster for testing.
We tried to copy a large folder which contains many files, and a large VHD file we created.
The result is the same - it will not restart the copy after failover. Thus as you said it is not caused by design and it should be an issue on your side which causes a Delete and redo the copy.
Is there any application or specific network settings could terminate a disconnected copy process? Currently I do not have much information about this.
Edit: I noticed that it is NFS share and in our test we are using SMB share. Will do the test again to see if any difference.

NFS makes OSX hang

Normally if you are connected to an NFS server and the connection goes down, the Finder tries to reconnect and if it can't, it unmount the partition.
But if a partition is not connected but it still mounted while Mac OS X is shutting down, this is not done properly, actually OS X hangs.
Is this happening to me only?
iMac G5 Mac OS X (10.4.3)

You're right, this is a major bug. Finder takes a lot of time to unmount disconnected shares (please consider that this could happen accidentally with low WiFi signal, for instance) and the kernel stop responding if this is happening during the shutdown process. This should be fixed soon.
Maybe nobody answered because NFS is used in advanced UNIX - Mac (Linux in my case) networks, and this is not exactly a standard home configuration.
I don't know if this happens with SMB or ftp, anyway Mac OS X shows an overall weakness with networks mounts of any kind, if connection suddenly goes down.

Old NFS Volumes are a problem in finder

Hi,
I mount an nfs volume and work on files that are saved on it. I do this manually in finder->Go->Connect to server
Sometimes it gets disconnected so I do that again, but there is a problem. The previous volume still exists in the directory. You can't access anything there or save anything there and when you re connect you get a new volume /volumes/server-1 or /volumes/server-2 or whatever comes next.
This is a problem, because any shortcuts don't work when this -n is appended to the server name, and when you try to save documents you have been working on, they won't save.
Can anyone suggest how to maybe automate the removal of these old entries in the directory. Any advice is appreciated.

Well, the lookup (which is dont via the findByPrimaryKey) is done to populate the fields in the entity. If, as you say, the mapping don't match (ie, a String value from the db trying to be put into a Long object) you will most likely get some error. The error message might not be that explicit, but you obviously MUST either change the mapping type or convert the column to what the mapping type says.
Cheers

Need NFS help... getting hangs on write

Hi all.
I'm having major problems with getting an NFS export to operate correctly for clients. I shared a dir over NFS, exported to subnet/mask, maproot to all. Right now it mounts ok, and users can read the files perfectly. But if you try to write at all it will immediately fail.
My logs start coming up with:
kernel[0]: nfs server server:/Volumes/drive: not responding
and this repeats about 20 times total. Amidst those this block appears:
KernelEventAgent[31]: tid 00000000 received VQ_NOTRESP event (1)
KernelEventAgent[31]: tid 00000000 type 'nfs', mounted on '/server/drive', from 'server:/Volumes/drive', not responding
KernelEventAgent[31]: tid 00000000 found 1 filesystem(s) with problem(s)
The disconnect drive window eventually pops up which stops the repetitions with this final message:
KernelEventAgent[31]: tid 00000000 unmounting 1 filesystems
I have no idea what to do here. On another xserve (a cluster), I tested NFS export the same way which worked fine. Granted, no other services were active.
Does anyone know what this is, or have any advice on how to get it working properly?
Mac OS X (10.4.6)

Hm... our network is running with jumbo frames... i will check to see if these larger frame sizes dont have something to do with the problem.
It's a good start at least.
As for the ports... yeah, the system is behind a network firewall, so all internal firewalls are down and shouldnt be affecting this traffic.

FTP performance over NFS 3

Hi Guys,
I have a NFS mount from one solaris OS to another solaris OS, When i do FTP to the NFS mounted server i get disconnected during "cd" to one particular directory. There are 500000+ files in that directory of total size 50GB.
My NFS stat is as below. I will like to know if there is any way to cache the file count information on nfs client side or any way to improve the performance to resolve FTP issue.
---cut---
Flags: vers=3,proto=tcp,sec=sys,hard,intr,link,symlink,acl,rsize=1048576,wsize=32768,retrans=5,timeo=600
Attr cache: acregmin=3,acregmax=60,acdirmin=30,acdirmax=60
---cut---
Thanks
Rahul

Hi;
Please check below links which could heplful for your issue:
Using NFS with ASM…
http://www.oracle-base.com/blog/2010/05/04/using-nfs-with-asm/
Oracle NetApp white paper..
http://www.oracle.com/technology/products/database/asm/pdf/netapp_asm3329.pdf
http://kevinclosson.wordpress.com/kevin-closson-index/cfs-nfs-asm-topics/
Regard
Helios

Unplumb net0 in public network, the HA NFS service didn't failover

I have two node consisting the cluster 4.1. I set up the NFS service on the cluster, as below.
root@sgh28h13:~# scstat -g
-- Resource Groups and Resources --
Group Name Resources
Resources: resource-group-1 sgh28cluster global_Sym_R5_1G_d110-rs nfs-global-Sym_R5_1G-d110-admin-rs
-- Resource Groups --
Group Name Node Name State Suspended
Group: resource-group-1 sgh28h13 Online No
Group: resource-group-1 sgh28h17 Offline No
-- Resources --
Resource Name Node Name State Status Message
Resource: sgh28cluster sgh28h13 Online Online - LogicalHostname online.
Resource: sgh28cluster sgh28h17 Offline Offline
Resource: global_Sym_R5_1G_d110-rs sgh28h13 Online Online
Resource: global_Sym_R5_1G_d110-rs sgh28h17 Offline Offline
Resource: nfs-global-Sym_R5_1G-d110-admin-rs sgh28h13 Online Online - Service is online.
Resource: nfs-global-Sym_R5_1G-d110-admin-rs sgh28h17 Offline Offline
The NFS service is on sgh28h13 originally. sgh28h13 has one interface net0 in public network for this service. So I use "ifconfig unplumb net0" to shutdown net0 so the NFS service could failover to the other node. But the service is still online on sgh28h13 after I shutdown the net0 and sc_ipmp0. I don't know why the NFS service didn't failover. Could somebody help?
root@sgh28h13:~# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
clprivnet0 ip ok -- --
lo0 loopback ok -- --
lo0/v4 static ok -- 127.0.0.1/8
lo0/v6 static ok -- ::1/128
net0 ip ok sc_ipmp0 --
net1 ip ok -- --
net2 ip ok -- --
sc_ipmp0 ipmp ok -- --
sc_ipmp0/static1 static ok -- 10.103.117.103/22
帖子经 user9111646编辑过

Hi.
IPMP not triggered on change or misconfigured configuration. You change configuration, so change configuration of IPMP to.
So cluster not trigered on this event.
In case you test failover for lost netowrk connections - initiate link down from switch side or just disconnect cable.
Regards.

NFS Troubles

I'm having a terrible time with NFS clients on OSX going to an ubuntu server 9.04 nfs share.
Basically I have a media server that works great with linux->linux connections, and even my set top box(tvix)->linux connections. When I try connections from OSX->linux it looks ok, browsing, and through terminal checking out the share etc, but as soon as I try to add media from the share to itunes(leaving the files on the share) or even now with songbird, the application hangs and throws a bunch of errors on the linux side:
[244474.431263] sd 3:0:0:0: [sdd] Add. Sense: Unrecovered read error - auto reallocate failed
Sep 14 11:23:24 Saturn kernel: [244474.431385] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVERSENSE,SUGGESTOK
Sep 14 11:23:24 Saturn kernel: [244474.431390] sd 3:0:0:0: [sdd] Sense Key : Medium Error [current] [descriptor]
Sep 14 11:23:24 Saturn kernel: [244474.431396] Descriptor sense data with sense descriptors (in hex):
Sep 14 11:23:24 Saturn kernel: [244474.431400] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 14 11:23:24 Saturn kernel: [244474.431412] 1c 41 ce 98
Sep 14 11:23:24 Saturn kernel: [244474.431417] sd 3:0:0:0: [sdd] Add. Sense: Unrecovered read error - auto reallocate failed
Sep 14 11:23:24 Saturn kernel: [244474.431485] ata4: EH complete
Sep 14 11:23:24 Saturn kernel: [244474.431553] sd 3:0:0:0: [sdd] 3907029168 512-byte hardware sectors: (2.00 TB/1.81 TiB)
Sep 14 11:23:24 Saturn kernel: [244474.431583] sd 3:0:0:0: [sdd] Write Protect is off
Sep 14 11:23:24 Saturn kernel: [244474.431634] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
The nfs share is exported as read only on the server side, and in diriectory utility i have it set as read only, and am using -P as another option.
I've also noticed that when its not read only, it corrupts files on the linux box. The share is a reiserfs LVM2 logical volume group across 3 drives.
What really baffles me is it runs fine from linux. I've been able to import all the music to amarok on my ubuntu work laptop so I really feel that something is not set correct on the OSX nfs client. any help would be appreciated as I don't want to dupe the music on the mac just so my wife can load her ipod.
this is on a gigibit network btw.

Mike Mackovitch wrote:
the application hangs and throws a bunch of errors on the linux side:
Those look like drive errors.
Nothing an NFS client can do should be able to cause those.
I would hope so, however I only get those errors on the server side when I try to run itunes from the mac to the share. The share is setup using "directory manager"
Does anything get logged in the Mac's /var/log/system.log (and/or /var/log/kernel.log on 10.6)?
checking, having trouble recreating today as now when I open itunes, I get share disconnect messages; even though I can go to the share through finder and play music with vlc; Does itunes not play well with automount? I think that's how directory manager sets up the share
I've also noticed that when its not read only, it corrupts files on the linux box.
How so? Is the NFS client actually trying to write to the files?
I wouldn't think so, I've just noticed that whenever I fought with itunes and NFS in the past, files randomly got set to ???? permissions on the server side; I would hope that brand new month old drives could handle itunes reading files and a media player reading files at the same time. shouldn't cause file permissions to corrupt. a reboot fixes the issue;
Or is the corruption possibly related to the drive errors being logged by the Linux kernel?
I would by that, but the drive errors only happen when I futz with itunes on the mac->nfs shares
What really baffles me is it runs fine from linux.
I imagine iTunes is a very different beast from the programs you have on Linux. And thus it would have a significantly different access pattern.
Can you reproduce these problems without iTunes?
Can you read/copy the same files iTunes is trying to read?
reproduced with songbird loading library also; the files itunes is trying to read play fine on a media player, and on amarok on my linux laptop
Thanks
--macko

Autofs timeout while accessing to remote NFS mount

Following Apple recommendations, I switched to "Directory Utility" to configure NFS mounts. As far as I understand, if you do so, the mounts are handled by automount which is itself called by autofs. The good thing of this is that autofs is unmounting unused mounts (after a timeout of 3600 seconds as defined in /etc/autofs.conf). Any time you need the remote drive (Finder call, ls in Terminal..., opening file), autofs is remounting ressource. This is a nice behaviour... in theory.
I'm using some codes (written in IDL) that are reading and writing on that remote NFS server once every 5 minutes. Theoretically, autofs should be detecting these accesses and should keep the drive mounted. This is unfortunately not the case. The drive is unmounted 3600 seconds after I last accessed the mount through the Finder or with any other Application.
There is apparently no way to remove this "automated unmounting" feature. I tried to set the timeout delay to a very large number (1 day) but it still disconnects me after this delay, if I don't do anything else than running my IDL code. If I mount the NFS share with the "mount_nfs" command, it works perfectly, as it is not handled by autofs.
I wonder then if there is any recommandation on Apple's side in such a case, other than going back to traditional mount_nfs.

As you have discovered, automount/autofs is also an "auto-unmounter" and there is no way to remove that feature. Contrary to what one might think, the auto unmounting does NOT happen after a period of "inactivity" of the mount. This is because autofs has no way of knowing when an automounted file system was last accessed. So, instead it periodically attempts to unmount it - if it is busy it won't get unmounted - if it isn't busy it will get unmounted.
You can't disable this - but you can make the periodic unmounting so infrequent as to effectively disable the feature. Try setting the AUTOMOUNT_TIMEOUT interval to something really large - like 315360000 (which would be 10 years).
However, in theory, this auto-unmounting should not be a problem because if it does get unmounted then the next access to that file system should cause it to get mounted again. And all this should happen without the code that is accessing the automount knowing that it isn't always mounted. It should always be there when it is accessed. So, the usual response to someone asking how to disable the auto-unmounting is to ask why they think it is a problem.
(Oh, and you don't have to use "mount_nfs" - just "mount" should work to manually mount an NFS file system (that saves a little typing).)
HTH
--macko

Temporarily stop nfs service?

I have a MacBook Pro and Air, running 10.6.6. When I'm on a plane, I want to stop NFS, as it's constantly trying to remount NFS mounts that aren't accessible (that I have loaded in DiskUtility/NFS).
I find myself manually unmounting the nfs mounts about every 1-5 minutes.
But I'd prefer to temporarily disable the NFS service when on a plane. On normal Linux, I use /etc/inet.d/nfs stop and start. I've tried SystemStarter and nfsd, but neither seem to actually do anything.
Any ideas? I'd prefer not to remove my NFS mounts from DiskUtility each time I'm disconnected, I just want to disable them temporarily.
Thanks in advance for any help!
-Mark

I have a MacBook Pro and Air, running 10.6.6. When I'm on a plane, I want to stop NFS, as it's constantly trying to remount NFS mounts that aren't accessible (that I have loaded in DiskUtility/NFS).
I find myself manually unmounting the nfs mounts about every 1-5 minutes.
But I'd prefer to temporarily disable the NFS service when on a plane. On normal Linux, I use /etc/inet.d/nfs stop and start. I've tried SystemStarter and nfsd, but neither seem to actually do anything.
Any ideas? I'd prefer not to remove my NFS mounts from DiskUtility each time I'm disconnected, I just want to disable them temporarily.
Thanks in advance for any help!
-Mark

Can't Shake NFS Automount, please HELP!

Mac connects directly to cable modem.
Problem? Something keeps grabbing me when I go online... my Mac cannot change it's IP address.
Folder called automount gets created upon reboot.
Network icon - get info - shows the following: Kind of file is Alias. It is located at /Network. Server is nfs://automount%20-nsl%20%5B197.
I've been getting this forever - If I get rid of it, it reappers.
I have no network here, I'm a home user.
My Windoze doesn't have this automount and gets a new IP each time... but my Mac is locked.
Can anyone please help me?
PS - I've tried DHCP renew, it doesn't work at all, nothing happens. My ISP is clueless about this. I believe it is locking onto a static IP but I'm not the one making it do it!

You report that you're connecting the Mac directly to a Motorola Surfboard without a router. What model Surfboard? (There should be a sticker on the bottom) How is the Windows PC connected to the internet? I have a Mottorola Surfboard at home driving a Mac and Pc, but through an Airport Basestation / router. I suspect that putting a basic four-port US$30 router between the modem and the Mac would help. Note that the Motorola Surfboard FAQ notes that multiple computer support requires a separate router. If you just switch the Ethernet cable from the modem between the PC and the Mac, or connect the Mac via Ethernet and the PC via USB, the modem doesn't accept the Mac's MAC (heardware-specific Media Access Code) after grabbing the PC's MAC code on power up. Putting a router between modem and computers and resetting the modem along with restarting the computers will force the modem to grab the router's MAC, and the router will then serve private-network IPs to the attached computers. Any router currrently on the market will also give you a NAT firewall as well; this hardware firewall can safely be used along with the OS X and Windows software firewalls and can greatly increase the security of your computers (especially the Windows one).
Also from the Motorola FAQ:My computer keeps pulling a 169.254.x.x IP address, the modem has been reset and power cycled and the computer is still getting the same IP address, how do I correct this?
Disconnect the Coax cable from the modem and restart it. Once the "Receive" light begins flashing reboot your computer. If the modem and the computer are communicating, the computer will get a 192.168.100.11 IP address (192.168.0.x with the SBG900) from the cable modem. Shut down your computer. Connect the Coax cable to the cable modem, restart it, and wait for the modem to sync up with the cable company. Once the modem is in sync (Power, Receive, Send, On-line are all illuminated) restart the computer. Once the computer has restarted check the IP address. The computer should have a valid IP address from the cable company. Computers attached to the SBG900 will always get a private (192.168.0.x) address regardless of whether or not the SBG900 is registered on the cable system.

[solved] NFS: "ls: reading directory .: Input/output error" after time

Hello,
I got the following configuration:
NFS-server: Always on, connected via LAN.
NFS-clients: 2 computers, connected via LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.
This works flawlessly some hours or even days. But after some time, the following happens:
1. mount nfs-share: no error message
2a. trying to access that folder via filemanager, e.g. thunar: folder seems to be empty (it isn't on server!), but the correct freesize of the NFS-share on server is displayed in the statusbar.
2b. trying to access that folder via commandline:
$ ls
ls: reading directory .: Input/output error
The very same worked just a few hours before, I haven't changed anything meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual mount NFS-share) on the clients which worked before, too.
Any idea what's going wrong?
additional info:
server:
/etc/exports
/srv/nfs/myshare 192.168.2.0/24(rw,all_squash,anonuid=33,anongid=33,no_subtree_check)
(yes, the mapping is needed and right.)
clients:
/etc/fstab
servername:/srv/nfs/myshare /home/carl/nfs nfs4 noauto,soft,user,_netdev,timeo=14,rsize=8192,wsize=8192 0 0
/usr/lib/systemd/system-sleep/umount-nfs
#!/bin/sh
case $1 in
pre)
umount -f /home/carl/nfs
esac
Last edited by Carl Karl (2014-09-21 17:07:47)

Indeed, there could be something interesting in dmesg on the server:
[ 4.190117] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 4.190596] NFSD: starting 90-second grace period (net ffffffff818a9540)
[ 5.445237] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 5.895519] r8169 0000:04:00.0 enp4s0: link up
[ 5.895529] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
[72346.265850] usb 3-1: USB disconnect, device number 2
[72346.670926] usb 3-1: new SuperSpeed USB device number 3 using xhci_hcd
[72346.684585] usb-storage 3-1:1.0: USB Mass Storage device detected
[72346.684716] scsi5 : usb-storage 3-1:1.0
[72347.686518] scsi 5:0:0:0: Direct-Access WD Elements 1048 1022 PQ: 0 ANSI: 6
[72347.687606] sd 5:0:0:0: [sdc] 976769024 512-byte logical blocks: (500 GB/465 GiB)
[72347.690295] sd 5:0:0:0: [sdc] Write Protect is off
[72347.690301] sd 5:0:0:0: [sdc] Mode Sense: 47 00 10 08
[72347.692981] sd 5:0:0:0: [sdc] No Caching mode page found
[72347.693025] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[72348.135398] sdc: sdc1
[72348.141458] sd 5:0:0:0: [sdc] Attached SCSI disk
[72348.455737] EXT4-fs (sdc1): recovery complete
[72348.455919] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[74276.020331] EXT4-fs error (device sda1): ext4_find_entry:1310: inode #14024711: comm nfsd: reading directory lblock 0
[74276.021107] EXT4-fs error (device sda1): ext4_find_entry:1310: inode #14024711: comm nfsd: reading directory lblock 0
(last one repeats several times...)
Indeed, the NFS-share resists on a external WD harddrive connected via USB, /dev/sdc1.
As suggested in the NFS wiki article, the NFS-share is a bind-mount:
/etc/fstab on server:
# fake-root for NFS
/magnet/owncloud/data/carl/files /srv/nfs/myshare none bind,noauto,x-systemd.automount
while /srv is on /dev/sda1.
The external harddrive has an auto-standby (NOT hdparm...) which isn't causing troubles with other services.
So it seems to be a problem connected to this bind-mount to external USB setup....
I'll try to find out whether there is a way to avoid that.
Thanks so far!
Last edited by Carl Karl (2014-09-16 14:30:02)

NFS Disconnected

Similar Messages

Maybe you are looking for