Bruce DeVisser wrote:
> Oops, forgot one thing:
>
> On Mon, Jun 30, 2003 at 01:20:51PM -0400, Bruce DeVisser wrote:
>
>>The scenario: after some development, I tagged a piece of
>>the trunk by copying to the repository tags directory.
>>Afterward, I created a development branch of the entire
>>trunk. I attempted svn switch to the branch, but it
>>failed, saying there was no space on the device (actually
>>there was double the size of the entire repository
>>available).
>
>
> Prior to all of this, I had run out of disk quota during a
> minor commit, and requested more. I ran svn cleanup
> immediately after obtaining it, just in case.
svn cleanup won't do you much good if you ran out of disk space on the
filesystem the repository lives on, it just cleans up the working copy,
it doesn't touch the repository at all. i imagine svnadmin recover
would be the way to go in such a case, but someone with more
filesystem-fu would be able to answer better.
> And, this raises another question about recovery: how is
> this 'replay' done? Is it just a matter of plugging in the
> log files and running svnadmin recover? (I got an error when
> I tried this, but didn't have the presence of mind to write
> it down.) In any case, it is not entirely clear to me from
> the documentation (even the BD documentation). But it is
> possible I just haven't found the right spot in the docs.
I would also be interested in exactly how to do this.
Also, I believe you mentioned that you were using ra_local to access a
repository on a network drive, right? That's a really bad idea, as
berkeley db doesn't play nicely with networked filesystems, and bad
things are likely to happen as a result.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 1 01:56:46 2003