|
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On 3-Mar-06, at 3:41 PM, Jon Peatfield wrote:
Just re-reading and seeing this part of your post - I've seen this before also. When this happens can you check the NFS ops and CPU usage on your machine that's exporting the mount. When I've seen this (Specifically I've seen it from large appliances like NetApp etc) the Mac system is making a call for a file which the NFS server is actually reporting doesn't exist, however the mac will repeat request this nonexistent file several times (even more if this is your home directory and you have an anti-virus on demand scanner running). Once you get several macs all requesting files at the same time our file servers were getting so overtaxed by as little as 10-15 client workstations that the NFS ops would be through the roof, and the CPU usage was pegged at 100% - thus causing some other machines to get a message that the file server was no longer responding - interestingly if the user left this error, and didn't tell is to unmount the file system it would often go away of it's own accord once the file server was allowed to relax a bit. Cheers, Andrina -- Systems Integrator IronGate Server Management & Consulting Toll-free: (866) 838-IRON (4766) Web site: www.irongate.ca |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macosx-interop mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
| References: | |
| >NFS (OSX client) problems (hanging machines) (From: Jon Peatfield <email@hidden>) |
| Home | Archives | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2011 Apple Inc. All rights reserved.