Hello Plamen!
On Monday 18 August 2008 MMM MMM wrote:
> Recently I upgraded VirtualBox from version 1.5.6 to 1.6.4. Then I decide
> to revert. I decide to use fsvs and I failed.
...
> I want to revert revision 85
> Or
> I want to update to revision 84
What has changed in these revisions? What does "fsvs log -v -r85:87" say?
> 1) 'sudo fsvs update -r 84' failed with msg "permissions denied" - it try
> to update directory /dev and it failed.
What kind of filesystem is your /dev?
> 2) 'sudo fsvs export -r 84' failed with msg "killed" - I am not sure but I
> think it means "out of memory"
That's one possibility. Did you run into swap heavily?
I've seen that message when using "svn+ssh://"-urls, because the APR
libraries unconditionally kill the ssh-subprocess.
> 3.1) 'sudo fsvs revert -r 85 -R -CC /' - failed, again problems with
> directory '/dev'.
Yes, update is mostly the same as revert.
> 3.2) 'sudo fsvs revert -r 85 -R -CC /[^d]*' - this is working but looks
> strange. Many times it stops with an err msg. When I run again the same
> command it continue and stop with different err msg. Sometimes it did not
> continue.
Hmmm ... what kind of error message was that?
Could you please try
sudo fsvs revert -r 85 -R -CC /[^d]* -o debug_output="| tail -500 >
/tmp/logfile" -d
and send me the logfile when it shows these symptoms?
> 3.3) 'sudo fsvs revert -r 85 -R -CC /[^dv]* /var/[^rl]*' - finally I
> switched to single user mode. If any error, I delete file/directory and run
> revert again. Finally I also excluded /var/run and /var/lock - maybe you
> know why better than me.
Well, without seeing the error message it is a bit hard.
The only thing I could imagine would be "text file busy" - but that
could only happen if some now-running program should get changed somehow.
I don't think that can happen for device nodes.
If the debug log file above doesn't help I might need you to call strace -
but we'll see.
> So... what are my mistakes?
None, these are exactly the things that should work.
> I understand, I did not 'revert working copy offline' (booting different
> linux) but... this task looks very simple... I just want to revert and
> VirtualBox is just a program.
Yes, it should Just Work(TM).
> I got many and different errors from fsvs. Maybe I do not understand how it
> works. Most important is that my system is NOT ready for crash and I am NOT
> ready to recover it.
I'm sorry that FSVS disappointed you. No, you seem completely competent,
I've seen much worse.
If it's a bit of consolation to you - the data in the repository isn't lost,
so even if your harddisk crashed you definitly *can* get the data back.
If everything else is lost, "mkfs" and "fsvs checkout" should never fail.
> Today I got some different errors (I am using ubuntu gutsy):
> > localpc:/$ fsvs -V
> > FSVS (licensed under the GPLv3), (C) by Ph. Marek; version trunk:1842
> >
> > localpc:/$ sudo fsvs commit -m 'backup 2008-08-18'
> > Committing to file://localhost/media/sda6/backup/fsvs/trunk/base
> > .m.. dir sys
> > .m.. dir proc
> > .mC. dir dev
> > .m.. dir dev/pts
> > .m.. dev dev/pts/0
> > .m.. dev dev/pts/1
> > An error occurred: Transaction is out of date (160028)
> > in ci__directory: open_file
>
> I do not know what is "Transaction is out of date". I decide that I did
> something wrong (I am trying my best and I have no idea what could be
> wrong).
"transaction out of date" is a subversion error message.
It seems that FSVS already thinks it could "update" to r84 or r85; now
FSVS tries to send a new revision to the repository, but that says
"why are you still at r84? I'm already at r87, you're out of date!"
(Sorry for that translation, I cannot make it clearer - just ask again,
then I'll try to rephrase that.)
Some more hits for that message:
http://www.google.de/search?hl=de&q=%22transaction+out+of+date%22&btnG=Suche&meta=
> I checked and I assume, my system is working (after all updates/reverts).
> So, I try to sync-repos (kind of 'delete and rebuld data in $FSVS_WAA').
> ((PS: also google answer is 'sync-repos')).
"sync-repos" just tells FSVS to get the filelist from the repository; it
might make sense to call
fsvs sync-repos -r84 -q
to make FSVS get the list from r84, and look what's different to that
(target) state.
Then "revert" should be possible; although, to avoid a "out of date"
error again, you'd have to "sync-repos" again, so that FSVS thinks it
has the HEAD revision locally, with some changes.
I can talk you through that on #fsvs, if you like.
> Again I got error:
> > localpc:/$ sudo fsvs sync-repos
>
> .......
>
> > N... 0 dev/ptyb8
> > N... 0 dev/ttypf
> > N... 0 dev/usbdev2.1_ep81
> > N... 0 dev/ptyb9
> > N... 0 dev/ptyaa
> > N... dir dev
> > N... dir sys
> > ..C. dir .
> > Killed
> > localpc:/$ _
That looks like the apr libraries killed a ssh process.
So that's no worry.
> What to do? Any comments are welcome (plus I am online in IRC #fsvs).
I'll see you there in about half an hour or so.
> Thank you in advance.
You're welcome - I appreciate help, and if it's real live testing
(and not just my small use-cases) it's worth even more.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
