[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: commit, with working copy on SMB share not working

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-04-13 12:52:08 CEST

On Apr 13, 2006, at 08:30, Peter Welte wrote:

> Has anyone had troubles checking out a working copy into a directory
> which is on a SMB share? Problems seem to occur with empty files in
> the repository, or (as shown below) when attempting to commit empty
> files.

I also experienced insurmountable problems attempting to use Samba-
mounted working copies from Mac OS X 10.4 (currently 10.4.6 PPC). We
have our repository on a Linux server and our working copies on a
Samba mount of that server, and attempting to manipulate these
working copies with Subversion running locally on the Mac always
results in heartbreak:

$ svn co https://www.example.com/svn/rschmidt
A rschmidt/foo
A rschmidt/foo/bar
svn: In directory 'rschmidt/foo'
svn: Can't copy 'rschmidt/foo/.svn/tmp/text-base/bar.svn-base' to
'rschmidt/foo/bar.tmp': Input/output error

Your observation that this only affects empty files is interesting.
"bar" above is indeed an empty file. I added a new directory "a" and
a non-empty file "baz" (from the Linux machine directly) but that
didn't work much better when checked out on the Mac:

$ svn co https://www.example.com/svn/rschmidt
A rschmidt/a
A rschmidt/a/baz
svn: In directory 'rschmidt/a'
svn: Error processing command 'readonly' in 'rschmidt/a'
svn: Can't set file 'rschmidt/a/.svn/text-base/baz.svn-base' read-
only: No such file or directory

I haven't been sufficiently motivated to attempt to track down why
this is, since I'm the only Mac user in the company, and all the
Windows users have no trouble using TortoiseSVN to control their
Samba-mounted working copies. In my case, I've cut Samba out of the
loop by either checking out local working copies on my Mac's hard
drive, or by opening an SSH session to the Linux server and running
my svn commands there. But it would certainly be preferrable if this
"just worked."

What I did observe is that all files and directories on the Samba
mount appear to be owned by my user and group, and to have 700
permissions. But I don't know if that's relevant. I do know that this
changed from Mac OS X 10.3.9, but I don't recall what the ownership
or permissions were before, nor whether Subversion worked with Samba-
mounted working copies then.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 13 12:53:22 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.