You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Bernd.Hofner@gmx.net" <be...@gmx.net> on 2003/08/07 12:06:45 UTC
Repository data integrity problem: continued
regarding my last straw mentioned in the previous mail:
[d:\develop\stempel wolf\temp]svnadmin dump P:\DevRep > DevRepDump
* Dumped revision 0.
svn: Filesystem has no such node-rev-id
svn: reference to non-existent node `o.0.1' in filesystem `P:/DevRep/db'
So restoring the repository via the dump won't be an option...
bernd hofner | diesterwegstr. 3 | 57078 siegen germany
tel: +49 (0)271/20266 | fax: +49 (0)271/20758 | mobile: +49 (0)170/2813683
Mail: Bernd.Hofner@gmx.net
Re: Repository data integrity problem: continued
Posted by "Bernd.Hofner@gmx.net" <be...@gmx.net>.
Why shouldn't it come as a surprise? I remember reading somewhere something
about problems with NFS drives,
although I seem not be able to find that in the subversion documentation
(book.pdf). I don't know where I read that...
I searched for "NFS", "SMB", "network drive", and even "shared" and couldn't
find anything mentioned about problems with shared drives on Windows.
So is there a problem with SMB shares and why?
Regards,
Bernd
----- Original Message -----
From: "mark benedetto king" <mb...@lowlatency.com>
To: <cm...@collab.net>
Cc: "Bernd.Hofner@gmx.net" <be...@gmx.net>;
<de...@subversion.tigris.org>
Sent: Friday, August 08, 2003 7:37 PM
Subject: Re: Repository data integrity problem: continued
> On Fri, Aug 08, 2003 at 12:37:09AM -0500, cmpilato@collab.net wrote:
> > "Bernd.Hofner@gmx.net" <be...@gmx.net> writes:
> >
> > > regarding my last straw mentioned in the previous mail:
> > >
> > > [d:\develop\stempel wolf\temp]svnadmin dump P:\DevRep > DevRepDump
> > > * Dumped revision 0.
> > > svn: Filesystem has no such node-rev-id
> > > svn: reference to non-existent node `o.0.1' in filesystem
`P:/DevRep/db'
> > >
> > > So restoring the repository via the dump won't be an option...
> >
> > I can probably recover any non-damaged portions of your repository.
> > Send me a URL to a tarball I can snatch.
> >
> > But, of course, I'd really like to know what the heck happened to the
> > repository.
> >
>
> The "P:" might be a good hint. If that is a network drive, then the
> repository corruption should come as no surprise.
>
> --ben
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository data integrity problem: continued
Posted by mark benedetto king <mb...@lowlatency.com>.
On Fri, Aug 08, 2003 at 12:37:09AM -0500, cmpilato@collab.net wrote:
> "Bernd.Hofner@gmx.net" <be...@gmx.net> writes:
>
> > regarding my last straw mentioned in the previous mail:
> >
> > [d:\develop\stempel wolf\temp]svnadmin dump P:\DevRep > DevRepDump
> > * Dumped revision 0.
> > svn: Filesystem has no such node-rev-id
> > svn: reference to non-existent node `o.0.1' in filesystem `P:/DevRep/db'
> >
> > So restoring the repository via the dump won't be an option...
>
> I can probably recover any non-damaged portions of your repository.
> Send me a URL to a tarball I can snatch.
>
> But, of course, I'd really like to know what the heck happened to the
> repository.
>
The "P:" might be a good hint. If that is a network drive, then the
repository corruption should come as no surprise.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository data integrity problem: continued
Posted by "Bernd.Hofner@gmx.net" <be...@gmx.net>.
Ah, now I know again where I read the NFS thing problem...
Although, as I am working alone, I don't think there was simultaneous access
to the repository.
But I can't be a 100% certain...
Alas, I will refrain from accessing the repository via the networked "p:"
drive and will use Apache WebDAV instead.
Maybe the documentation should warn people off using a networked drive for
the repository...
Well, thanks for the hint!
Bernd
----- Original Message -----
From: <cm...@collab.net>
To: "Bernd.Hofner@gmx.net" <be...@gmx.net>
Cc: "Subversion Developers" <de...@subversion.tigris.org>
Sent: Friday, August 08, 2003 7:52 PM
Subject: Re: Repository data integrity problem: continued
> "Bernd.Hofner@gmx.net" <be...@gmx.net> writes:
>
> > Further debugging hint:
> > I need a "mobile" repository because I often go out to the customers
> > working there without Internet access. So I put the repository on a
> > mobile disk which is mounted as drive "P:" on the local machine. To
> > access it from my laptop via my "Intranet", I mounted the
> > corresponding network drive also to "P:".
> >
> > Now if I go out for a longer time, I could attach the mobile drive
> > to my laptop directly, also using the drive letter "P:". This saves
> > me the effort of relocating the repository URL in the WC (I hope).
> > Could there be a problem with the mapped network drive?
>
> Yeah, there sure could. Berkeley is known to have issues on networked
> drives. (Digging up the URL now...)
>
> (Ah, there it is!).
>
> http://www.sleepycat.com/docs/ref/env/remote.html
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository data integrity problem: continued
Posted by cm...@collab.net.
"Bernd.Hofner@gmx.net" <be...@gmx.net> writes:
> Further debugging hint:
> I need a "mobile" repository because I often go out to the customers
> working there without Internet access. So I put the repository on a
> mobile disk which is mounted as drive "P:" on the local machine. To
> access it from my laptop via my "Intranet", I mounted the
> corresponding network drive also to "P:".
>
> Now if I go out for a longer time, I could attach the mobile drive
> to my laptop directly, also using the drive letter "P:". This saves
> me the effort of relocating the repository URL in the WC (I hope).
> Could there be a problem with the mapped network drive?
Yeah, there sure could. Berkeley is known to have issues on networked
drives. (Digging up the URL now...)
(Ah, there it is!).
http://www.sleepycat.com/docs/ref/env/remote.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository data integrity problem: continued
Posted by cm...@collab.net.
"Bernd.Hofner@gmx.net" <be...@gmx.net> writes:
> regarding my last straw mentioned in the previous mail:
>
> [d:\develop\stempel wolf\temp]svnadmin dump P:\DevRep > DevRepDump
> * Dumped revision 0.
> svn: Filesystem has no such node-rev-id
> svn: reference to non-existent node `o.0.1' in filesystem `P:/DevRep/db'
>
> So restoring the repository via the dump won't be an option...
I can probably recover any non-damaged portions of your repository.
Send me a URL to a tarball I can snatch.
But, of course, I'd really like to know what the heck happened to the
repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org