Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: FSVS 1.0.1 released

Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

Re: FSVS 1.0.1 released

Author pmarek
Full name P.Marek
Date 2005-10-05 03:23:20 PDT
Message I just found a problem in the 1.0.1 release if you happen to have
hardlinks in your filesystem.
Everything works fine, except that fsvs stops writing the .waa-dir file
with a message like
   "dir___f_sort_by_inode (directory[i-1], directory[i] ) >=0"

That's because in the DEBUG compilations (which are the default) there's a
faulty check for correctly sorted inodes, which basically tries to force
  inode1 < inode2 < inode3 < inode4 ...

This assumption breaks with hardlinks, where inodeX == inodeX+1.

So just change the >=0 in the given line (see file and linenumber in the
message) to a >0, and you'll be fine.

If you did a commit when it crashed, you can just do a
  fsvs ci -B
which re-creates and writes the list of files into the waa-area.




FSVS 1.0.1 released

Author pmarek
Full name P.Marek
Date 2005-10-04 23:55:40 PDT
Message Hello everybody!

I've just released 1.0.1, which has a few bugfixes - the most notable is
that it's using abort_commit when something bad happens.
I'm not sure if that's the Right Thing for a backup tool (which should
save as much as possible), but I'll have to re-do the user
confirmation/abort thing sometime.

No new features.

One performance update: "fsvs commit" uses the calculated MD5 (by
svn_delta_send_stream()), and doesn't recalculate again.
"fsvs status" doesn't calculate at all (unless requested with -C).

Please note the mail at
http://fsvs.tigris.o​rg/servlets/ReadMsg?​list=users&msgNo​=8 regarding

Happy testing!


Messages per page: