You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Peter Welte <we...@gmail.com> on 2006/04/13 06:30:16 UTC
commit, with working copy on SMB share not working
Hello all,
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.
specifics:
OS: Mac 10.4.6
svn version 1.3.1 (r19032)
repository is on http
SMB server is SAMBA (Version 3.0.10)
I haven't tried this on Windows or Linux yet. My repository is an
empty one created for testing. I have tried testing this where the
working copy is on a local hard drive, and also where the working copy
is on an NFS mount (and those two cases work).
Peters-Computer:~/netlauren/dbg lauren$ svn co http://athena/svn/repo/trunk repo
Checked out revision 1.
Peters-Computer:~/netlauren/dbg lauren$ cd repo/
Peters-Computer:~/netlauren/dbg/repo lauren$ ls
Peters-Computer:~/netlauren/dbg/repo lauren$ touch empty
Peters-Computer:~/netlauren/dbg/repo lauren$ svn stat
? empty
Peters-Computer:~/netlauren/dbg/repo lauren$ svn add empty
A empty
Peters-Computer:~/netlauren/dbg/repo lauren$ svn commit -m "add empty
file, commit will fail"
Adding empty
Transmitting file data .svn: Commit failed (details follow):
svn: Can't copy '/Volumes/LAUREN/dbg/repo/empty' to
'/Volumes/LAUREN/dbg/repo/.svn/tmp/text-base/empty.svn-base.tmp':
Input/output error
Peters-Computer:~/netlauren/dbg/repo lauren$ ls -l
total 0
-rwx------ 1 lauren admin 0 Apr 12 23:09 empty
Peters-Computer:~/netlauren/dbg/repo lauren$ ls -l .svn/tmp/text-base
total 0
-rwx------ 1 lauren admin 0 Apr 12 23:10 empty.svn-base.tmp
Adding non empty file works:
Peter-Computer:~/netlauren/dbg/repo lauren$ svn revert empty
Reverted 'empty'
Peter-Computer:~/netlauren/dbg/repo lauren$ svn stat
? empty
Peter-Computer:~/netlauren/dbg/repo lauren$ echo "hello" > nonempty
Peter-Computer:~/netlauren/dbg/repo lauren$ svn stat
? nonempty
? empty
Peter-Computer:~/netlauren/dbg/repo lauren$ svn add nonempty
A nonempty
Peter-Computer:~/netlauren/dbg/repo lauren$ svn commit -m "added
nonempty file, commit will work"
Adding nonempty
Transmitting file data .
Committed revision 2.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: commit, with working copy on SMB share not working
Posted by Ryan Schmidt <su...@ryandesign.com>.
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