On Mar 7, 2006, at 15:47, Markus Karg wrote:
> sure I can use my backup, but losing one day's work is not nice.
> The intention of asking the community was to find a solution that
> prevents losing one day of work.
> I have done a svnadmin verify and it didn't tell any errors. So I
> think the repository is ok. How to check the local filesystem? I've
> done a cleanup (no problems reported) and tried the commit again,
> but still there is the same error.
> Any ideas (other than: "Remove your local work and checkout from
If you can check out the code from the repository and your locally
changed files are still readable, you can check out to some other
place, copy your local changes over the top of the new working copy
(be careful no to mung the .svn directories) and then commit that.
After that, you can delete the original corrupt W/C and either check
out again or even move the second W/C to replace the original.
If you can no longer read the locally modified files, that's probably
the end of them.
> Mit freundlichem Gruss / With kind regards
> Markus KARG, Staatl. gepr. Inf.
> Entwicklung / R & D
> QUIPSY QUALITY GmbH
> Von: Karl Auer [mailto:email@example.com]
> Gesendet: Mo 06.03.2006 16:58
> An: firstname.lastname@example.org
> Betreff: Re: What to do?
> On Mon, 2006-03-06 at 16:11 +0100, Markus Karg wrote:
> > Filesystem is corrupt
> > svn: Commit failed (details follow):
> > svn: Ungültige Reihenfolge bei Änderung: Neue Knoten Revisions ID
> > Löschen
> Use your backups, Luke.
> Can you check out the latest revision? If so, maybe the filesystem
> talking about is yours, not the repository's.
> Regards, K.
> Karl Auer (email@example.com) +61-2-64957160
> http://www.biplane.com.au/~kauer/ +61-428-957160
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Tue Mar 7 07:59:29 2006