Cannot write to NFS mount with finder

hi folks
i have moved from a G4 cube running 10.4.9 to a new iMac running os x 10.5.7 (including upgrading from the old machine)
the NFS mounts i used to have with my G4 cube are not working properly; new mounts i've created aren't working properly either.
i can read/open file OK, but when i try to drag & drop files onto the NFS mount using the finder i get errors:
"You may need to enter the name and password for an administrator on this computer to change the item named test.jpg" [ stop ] [ continue ]
clicking "continue" i get:
"The item test.jpg contains one or more items you do not have permission to read. Do you want to copy the items you are allowed to read? [ stop ] [ continue ]
Choosing continue again results in the file appearing in the NFS directory, but with 0 size, and a time stamp of 1970.
if i try to copy the same file using the Terminal, it works fine - so it is not a simple NFS permissions problem - it is something particular to the Finder.
i am able to create a folder inside the NFS director by using the Finder.
i thought at first it might be related to the .DS_Store and similar files being written, so i tried turning off that behaviour:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
but that hasn't fixed the problem
there are no obvious messages in any of the logs
any suggestions or pointers on how to fix this?

thanks for the reply
these articles appear to relate to sharing a mac filesystem via NFS: exporting the data.
i am referring to mounting a NFS filesystem from another server onto the mac (leopard) client
the mounting works fine: it's just the finder which isn't behaving. the finder worked in tiger; isn't in leopard.

Similar Messages

  • Accessing NFS mounts in Finder

    I currently have trouble accessing NFS mounts with finder. The mount is O.K. I can access the directories on the NFS server in Terminal. However, in Finder when I click on the mount, instead of seeing the contents of the NFS mount I only see the "Alias" icon. Logs show nothing.
    I am not sure when it worked the last time. It could well be that the problem only started after one of the lastest snow leopard updates. I know it worked when I upgraded to Snow Leopard.
    Any ideas?

    Hello gvde,
    Two weeks ago I bought a NAS device that touted NFS as one of the features. As I am a fan of Unix boxes I chose an NAS that would support that protocol. I was disappointed to find out that my Macbook would not connect to it. As mentioned in previous posts (by others) on this forum, I could see my NFS share via the command line, but not when using Finder. I was getting pretty upset and racking my brain trying to figure it out. I called the NAS manufacturer which was no help. I used a Ubuntu LiveCD (which connected fine). I was about ready to give up. Then, in another forum someone had mentioned the NFS manager App.
    After I installed the app and attempted to configure my NFS shares, the app stated something along the lines of (paraphrasing) "default permissions were incorrect". It then asked me if I would authenticate to have the NFS manager fix the problem. I was at my wits end so I thought why not. Long story short, this app saved me! My shares survive a reboot, Finder is quick and snappy with displaying the network shares, and all is right with the world. Maybe in 10.6.3 Apple will have fixed the default permissions issue. Try the app. It's donationware. I hope this post helps someone else.
    http://www.macupdate.com/info.php/id/5984/nfs-manager

  • Cannot access external NFS mounts under Snow Leopard

    I was previously running Leopard (10.5.x) and automounted an Ubuntu (9.04 Jaunty) Linux NFS mount from my iMac. I had set this up with Directory Utility and it was instantly functional and I never had any issues. After upgrading to Snow Leopard, I set up the same mount point on the same machine (using Disk Utility now), without changing any of the export settings, and Disk Utility stated that the external server had responded and appeared to be working correctly. However, when attempting to access the share, I get a 'Operation not permitted' error. I also cannot manually create the NFS mount using mount or mount_nfs. I get a similar error if I try to cd into /net/<remote-machine>/<share>. I can see the shared folder in /net/<remote-machine>, but I cannot access it (cd, ls, etc). I can see on the Linux machine that the iMac has mounted the share (showmount -a), so the problem appears to be solely in the permissions. But I have not changed any of the permissions on the remote machine, and even then, they are blown wide open (777) so I'm not sure what is causing the issue. I have tried everything as both a regular user, and as root. Any thoughts?
    On the Linux NFS server:
    % cat /etc/exports
    /share 192.168.1.0/24(rw,sync,nosubtree_check,no_rootsquash)
    % showmount -a
    All mount points on <server>:
    192.168.1.100:/share <-- <server> address
    192.168.1.101:/share <-- iMac address
    On the iMac:
    % rpcinfo -t 192.168.1.100 nfs
    program 100003 version 2 ready and waiting
    program 100003 version 3 ready and waiting
    program 100003 version 4 ready and waiting
    % mount
    trigger on /net/<server>/share (autofs, automounted, nobrowse)
    % mount -t nfs 192.168.1.100:/share /Volumes/share1
    mount_nfs: /Volumes/share1: Operation not permitted

    My guess is that the Linux server is refusing NFS requests coming from a non-reserved (<1024) source port. If that's the case, adding "insecure" to the Linux export options should get it working. (Note: requiring the use of reserved ports doesn't actually make things any more secure on most networks, so the name of the option is a bit misleading.)
    If you were previously able to mount that same export from a Mac, you must have been specifying the "-o resvport" option and doing the mounts as root (via sudo or automount which happens to run as root). So that may be another fix.
    HTH
    --macko

  • IPod Cannot be updated or mounted with ipod updater or itunes

    Every time i try to update my ipod on itunes i either get "The iPod "Tdunks iPod" cannot be updated. The disk cannot be read from or written to." or i will get "The iPod "Tdunks iPod" cannot be updated. Required file not found." When i try to use ipod updater i get " Can't mount iPod" I have an ipod nano 2gb black version and am runnign windows xp with the newest itunes and ipod updater.

    try this, change the drive letter of the ipod this can sometimes solve your issue change it to "M" or something like that this is how to change it, Click on control panel/admin tools/computer management/disk management/right click on the iPod to re-assign the drive letter.
    iPods- 4gb Balck Nano, 60gb Black 5g}{Black Moto Razr}{PSP}{iPod Radio Remote   Windows XP   <img src="http://www.filehigh.com/serve/1/6566.gif"align="right"</span>

  • Accessing NFS mounted share in Finder no longer works in 10.5.3+

    I have setup an automounted NFS share previously with Leopard against a RHEL 5 server at the office. I had to go through a few loops to punch a hole through the appfirewall to get the share accessible in the Finder.
    A few months later when I returned to the office after a consultancy stint and upgrades to 10.5.3 and 10.5.4 the NFS mount no longer works. I have investigated it today and I can't get it to run even with the appfirewall disabled.
    I've been doing some troubleshooting, and the interaction between the statd, lockd and perhaps the portmap seem a bit fishy, even with the appfirewall disabled. Both the statd and lockd complains that they can not register; lockd once and statd indefinitely.
    Jul 2 15:17:10 ySubmarine com.apple.statd[521]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
    Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd[521]): Exited with exit code: 1
    Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
    ... and rpcinfo -p gets connection refused unless I start portmap using the launchctl utility.
    This may be a bit obscure, and I'm not exactly an expert of NFS, so I wonder if someone else stumbled across this, and can point me in the right direction?
    Johan

    Sorry for my late response, but I have finally got around to some trial and error. I can mount the share using mount_nfs (but need to use sudo), and it shows up as a mounted disk in the Finder. However, when I start to browse a directory on the share that I can write to, I end up with the lockd and statd failures.
    $ mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
    mount_nfs: /Users/yyyy/xxxx-home: Permission denied
    $ sudo mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
    Jul 7 10:37:34 zzzz com.apple.statd[253]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
    Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd[253]): Exited with exit code: 1
    Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
    Jul 7 10:37:44 zzzz com.apple.statd[254]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
    Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd[254]): Exited with exit code: 1
    Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
    Jul 7 10:37:54 zzzz com.apple.statd[255]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
    Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd[255]): Exited with exit code: 1
    Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
    Jul 7 10:37:58 zzzz loginwindow[25]: 1 server now unresponsive
    Jul 7 10:37:59 zzzz KernelEventAgent[26]: tid 00000000 unmounting 1 filesystems
    Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /net updated
    Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /home updated
    Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: no unmounts
    Jul 7 10:38:02 zzzz loginwindow[25]: No servers unresponsive
    ... and firewall wide open.
    I guess that the Finder somehow triggers file locking over NFS.

  • Permissions issue with NFS mounted MyCloud

    FIrst off let me say I think this is a LInux issue and not a WDMyCloud issue, but I'm not sure, so here goes... I can rsync my stuff off the  Linux systems on my LAN to back them up into a WDMyCloud share, no problem.  But then I can't get at some stuff with limited file permissions, when I mount the WDMyCloud via NFS. Here's the problem...  Let's s say my directory tree on the WDMyCloud looks like "/shares/Stuff/L1/L2/L3" where the permissions on "L3" look like this: drwx------+ 3 fred share 4096 Jul 1 01:03 L3 It's readable/writeable only by "fred".  I want to preserve the permissions and ownerships on everything, so if I have to do a restore and "rsync" it back onto another machine they'll go back the way they were when I backed them up.  I can see the contents of "L3" if I "ssh" into the MyCloud, *but* I *cannot* see the contents of  "L3" if I try to look at it via the NFS mount - I get ls: L3: permission denied. If I change the permissions on it, e.g.drwxrwxrwx+ 3 fred share 4096 Jul 1 01:03 L3then I can see the contents of "L3" just fine.  So it's just the fact that via the NFS mount the MyCloud NFS server (Or something?) won't give me access to it unless the permissions are open, even logged in as "root" on the machine where the MyCloud is NFS mounted. I tried creating "fred" as a user on the MyCloud *and* made sure the numerical UID and GIDs were the same on the Linux machine and the MyCloud - No dice. I haven't tried everything in the world yet (I haven't tried rebooting the MyCloud to see if some server hasn't picked up the changes to "/etc/passwd" or whatever ; there's something called "idmapd" that I guess I should look into...  Etc.)  But I thought maybe somebody here might have run into this or have a bright idea?  

    I had some problems, and I modified the /etc/exports file to meet a little more my needs This is the content of it: -------/nfs/jffs *(rw,sync,no_root_squash,no_subtree_check)/nfs *(rw,all_squash,sync,no_subtree_check,insecure,crossmnt,anonuid=999,anongid=1000)-------- The first line/share allows to change the permissisions and uid below them when you monted on your machineThe second one I maped the anonuid to the uid my user has on the wd (999) so when I mount a share on the machine everything is write with that used id If you modifes the /etc/exports file remeber to run after you edited the command "exportfs -a" to refresh the changes Hope this help with your problem

  • Anyone else having problems with NFS mounts not showing up?

    Since Lion, cannot see NFS shares anymore.  Folder that had them is still threre but the share will not mount.  Worked fine in 10.6.
    nfs://192.168.1.234/volume1/video
    /Volumes/DiskStation/video
    resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
    Any ideas?
    Thanks

    Since the NFS points show up in the terminal app, go to the local mount directory (i.e. the mount location in the NFS Mounts using Disk Utility) and do the following:
    First Create a Link file
    sudo ln -s full_local_path link_path_name
    sudo ln -s /Volumes/linux/projects/ linuxProjects
    Next Create a new directory say in the Root of the Host Drive (i.e. Macintosh HDD)
    sudo mkdir new_link_storage_directory
    sudo mkdir /Volumes/Macintosh\ HDD/Links
    Copy the Above Link file to the new directory
    sudo  mv link_path_name new_link_storage_directory
    sudo  mv linuxProjects /Volumes/Macintosh\ HDD/Links/
    Then in Finder locate the NEW_LINK_STORAGE_DIRECTORY and then the link file should allow opening of these NFS point points.
    Finally, after all links have been created and placed into the NEW..DIRECTORY, Place it into the left sidebar.  Now it works just like before.

  • Finder not refreshing file or folder names, in NFS mounts.

    We are experiencing the an issues with NFS mounts, in both 10.7 and 10.8 machines.  After mounting NFS shares, the file/folder names do not update in other MAC finder windows until it is unmounted and remounted on the MACs.  This DOES NOT happen in our 10.6.8 and earlier machines.

    Cross posted
    http://forum.java.sun.com/thread.jspa?threadID=768693&tstart=0

  • ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

    Hi,
    i am getting following error, while taking RMAN backup.
    ORA-01580: error creating control backup file /backup/snapcf_TST.f
    ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
    DB Version:10.2.0.4.0
    while taking datafiles i am not getting any errors , i am using same mount points for both (data&control files)

    [oracle@localhost dbs]$ oerr ora 27054
    27054, 00000, "NFS file system where the file is created or resides is not mounted with correct options"
    // *Cause:  The file was on an NFS partition and either reading the mount tab
    //          file failed or the partition wass not mounted with the correct
    //          mount option.
    // *Action: Make sure mount tab file has read access for Oracle user and
    //          the NFS partition where the file resides is mounted correctly.
    //          For the list of mount options to use refer to your platform
    //          specific documentation.

  • My first gen ipod mini does no longer sync with itunes 11.0. It says "cannot write or read". Ist this the end?

    My first gen ipod mini (that I use in my car) does no longer sync with itunes 11.0. It basically says "cannot write or read". Is this the "end of life" of that ipod?

    You mean you can't get to the Summary pane?
    If you  have iTunes 11 turn on the Sidebar. Go to iTunes>View and click on Show Sidebar. You can also do a Crtl+S to show the sidebar. The sidebar is where Devices appears. and Control+B to show the Menu bar

  • No longer mount NFS volumes with 2010.q1 release:

    Has anyone else seen this? I can no longer mount any of my NFS volumes with root squash since upgrading to 2010.q1. I have a ticket open with Sun (72644622), but everyone is apparently off/away.
    Before they all went off, Sun Eng. suggested setting max supported NFS version to 3, but this of course did not work. Hosts trying to mount the volumes error out with:
    call_verify: server HOST_IP_HERE requires stronger authentication.
    I have double checked that the atuh is set to sys (not krb), but it looks like the nfsd is not respecting this.
    Of course this has knocked all our VMware mounts offline as well, and using krb for these is out of the question....
    Had to update to support the new FC card...which works great...but me needs me nfs shares....
    Fishworks doods, stop yelling at drives and help a brother out ;)

    I wish I could tell you, but it seems we lost a CIM card. Worse yet, this failure was completely SILENT. Not a single "problem" listed in the logs. However, when attaching another J4400, I noticed an alarm LED on the failed CIM and verified that the storage was only seen by 1 path. Kind of disconcerting that availability could be reduced significantly without so much as an email.
    I'll let you know if we can get to the new release later this week.
    Charles

  • In a document with several sections, in section VIII and IX one cannot select the text of the page foot nor set the pointer in it; so, one cannot write nor change the page foot text. Please help!

    in a document with several sections, in section VIII and IX one cannot select the text of the page foot nor set the pointer in it; so, one cannot write nor change the page foot text. Please help!

    Question already asked and answered several times.
    It's a bug striking in long documents.
    Select a word somewhere higher in the page then use the arrows to reach the wanted insertion point.
    Yvan KOENIG (VALLAURIS, France) mardi 23 août 2011 15:44:24
    iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
    My iDisk is : <http://public.me.com/koenigyvan>
    Please :
    Search for questions similar to your own
    before submitting them to the community
    To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

  • Nfs mount created with Netinfo not shown by Directory Utility in Leopard

    On TIger I used to mount dynamically a few directories using NFS.
    To do so, I used NetInfo.
    I have upgraded to Leopard and the mounted directories
    are still working, although Netinfo is not present anymore.
    I was expecting to see these mount points and
    modify them using Directory Utility, which has substituted Netinfo.
    But they are not even shown in the Mount panel of Directory Utility.
    Is there a way to see and modify NFS mount point previously
    created by NetInfo with the new Directory Utility?

    Thank you very much! I was able to recreate the static automount that I had previously had. I just had to create the "mounts" directory in /var/db/dslocal/nodes/Default/ and then I saved the following text as a .plist file within "mounts".
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>dir</key>
    <array>
    <string>/Network/Backups</string>
    </array>
    <key>generateduid</key>
    <array>
    <string>0000000-0000-0000-0000-000000000000</string>
    </array>
    <key>name</key>
    <array>
    <string>server:/Backups</string>
    </array>
    <key>opts</key>
    <array>
    <string>url==afp://;AUTH=NO%20USER%[email protected]/Backups</string>
    </array>
    <key>vfstype</key>
    <array>
    <string>url</string>
    </array>
    </dict>
    </plist>
    I don't think the specific name of the .plist file matters, or the value for "generateduid". I'm listing all this info assuming that someone out there might care.
    I assume this would work for SMB shares also... if SMB worked, which it hasn't on my system since I installed leopard.

  • Cannot write email body in OWA with Exchange 2013 SP1 CU6

    Hi,
    I have a problem with Exchange 2013 SP1 with CU6.
    All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
    The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
    Have you an idea ?
    Thanks in advance!
    Sebastien

    Hi, 
    After contacting Microsoft support, we have found the solution.
    The problem appear after we have recently install the patch described in this KB 2997209:
    https://support.microsoft.com/kb/2997209?wa=wsignin1.0
    But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
    So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
    No need to reboot, or restart IIS, it's working after that!
    @+
    Sébastien

  • Strange delete behavior in Solaris 10 with NFS mounts

    We are using the apache commons-io framework to delete a directory in a Solaris 10 environment. The code works well on our dev and qa boxes, but when we load it into our production envrionment we get intermittent failures where the files in a directory are not being deleted and therefore when we try to delete the directory it fails to delete.
    We suspect that this may be some kind of NFS problem in Solaris where it may take longer to delete a file than if it is on a local drive and therefore the code reaches the deletedir before the OS actually removes the files and this cause the delete directory failure because files are still present.
    Has anyone seen this in an NFS environment with Solaris? We are on Java 1.4.2_15 and we are using apache commons-io 1.3.1.

    The apache commons-io framework contains a method to delete a directory by recursively deleting all files and subdirectories. Intermittently, we are seeing some of the files in a subdirectory remain and then when delete is called to remove the directory (from within the commons-io framework deletedir method) we get an IOException. This only occurs on an NFS mounted file system on our production system. Our dev and qa systems are also on an NFS but it is a different one and appears to be loaded differently and the behavior for dev and qa consistently works as expected.
    It appears to be some kind of latency issue related to the way java deletes files on the NFS, but no conclusive evidence so far.
    We have not tried this with a newer version of java since we are presently constrained to 1.4 :-(

Maybe you are looking for