Re: Issue on a mounted volume on osx
From: Mike Conley <nomad_at_crystalmaker.com>
Date: 2006-03-01 12:22:45 CET
On 01.03.2006, at 08.33 (UTC-0000), Simon Whittaker scribbled thusly:
>... I have a volume mounted on OSX 10.4.5 to a shared windows folder
I don't get exactly the same error, but I did report a similar problem back in December, to which I never received any response. Since there now appear to be two people on the planet who use a similar configuration, I'll repost my original report in the hopes that (a) it might be useful to you and (b) somebody might have an idea as to what's going on.
Subject: Another SVN Permissions Problem
I know this has been beaten to death, but, really, I have read the archives, and I have tried any number of things, and yet....
I have a repository sitting on a Mac OS X Server box. My working copy sits on a Windows box. I have the volumes mounted via Samba on my Mac running OS X 10.4.
Until this morning, I had no problems doing anything I wanted to on this setup. I could check code out to my Windows box using my Mac (via the OS X svn client directly from the command line or using BBEdit's SVN support). I could edit it, add new files, delete files, commit, whatever.
Now, all of a sudden, I find I can no longer do this. I constantly get errors indicating that I no longer have permissions to move things around. In response to an svn cleanup command, for example, I get
If I run the same command using TortoiseSVN directly on my Windows box, it appears to work fine.
If I delete the working copy and try to check out a new one from my Mac onto the Windows box, I usually get an I/O error from svn.
I can check out to my Mac just fine.
I've tried mounting the Windows volume using mount_smbfs directly, and setting the file and directory permissions to 0775 and 0777, respectively, with my user and group IDs, and I get the same problem.
This is highly frustrating, as I had a wonderfully smooth workflow going just yesterday. The only thing I've done since then was to do a whole slew of property changes to the files (clearing out extraneous svn:executable flags, setting svn:eol-style, etc.) in preparation for starting a new project in the repository. Somehow, it appears that that has completely screwed things up. Or is that the problem?
svnadmin verify seems to indicate that everything's fine.
Anyone have any ideas?
This is an archived mail posted to the Subversion Users mailing list.