http://blog.gmane.org/gmane.comp.sysutils.backup.fsvs.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/644 Hello everybody, I'm asking for a bit of help. With the next FSVS version there'll be some incompatible changes - the $FSVS_WAA has an additional level, and the URLs file has moved. Would somebody like to help me, writing a script that does the conversion? Regards, Phil Philipp Marek 2008-11-29T09:13:41 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/641 Hi, I'm still experimenting the use of a single FSVS repository with multiple identical servers. As I said before, it's a complicated setup with NFS subfolders, but I'll take a simpler example to describe my question. - I have 2 servers: server1 and server2. - They both have an indentical "/app" directory. Well, almost identical, we'll see.. - I version "/app" on server1 with FSVS. For example: cd /app fsvs urls name:base,prio:200,svn://10.10.10.10/project/trunk/app fsvs ignore ...... fsvs commit -m "First commit on server1" - Now I want to version server2 and synchronize it with server1. BUT, there is one subfolder I want to exclude from server2: "/app/peculiar". On server2, I run the following: cd /app fsvs urls name:base,prio:200,svn://10.10.10.10/project/trunk/app fsvs ignore ... fsvs ignore ./peculiar fsvs sync-repos - Now I want to check the status before commiting on server2. But whatever I do, "/app/peculiar" appears in "fsvs status".. - If I try to get rid of it locally with "unversion", it'll be deleted from the repository! fsvs unversion ./peculiar fsvs commit -m "First commit on server2" [.. FSVS deletes "./peculiar" from the SVN repository.. ] This is of course not what want: If I run "fsvs update" on "server1", its "app/peculiar" directory would be deleted! Is there a proper solution for this case? Otherwise is there a way to circumvent this? Regards Farzad FARID 2008-11-27T17:26:29 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/638 Hi, I have a strange problem on a system I'm setting up. As I already explained previously, the server "clusters" share NFS mount point right in the middle of the application directory I am versionning. - I already versionned the "/app/my_application" on SERVER1, including the 2 NFS mounted subdirectories (./settings and ./extension) - I am now versionning SERVER2. Here is what I did: cd /app/my_application fsvs urls N:..,P:..,<same svn url as server1> fsvs ignore <a bunch of files> fsvs ignore ./settings fsvs ignore ./extension I then run "fsvs sync-repos". All the file and directory names scroll on the screen, including those in ./settings and ./extension. Now I try to run "fsvs status", and it fails with an NFS error! [root< at >server2]# fsvs status D... 1113 clearlabels.php .m.. 1476 settings/binaryfile.ini .m.. 6944 settings/browse.ini .m.. 821 settings/codetemplate.ini [.................] .m.. 1296 settings/wordtoimage.ini .mC. 31861 settings/siteaccess/site_instit/override.ini.append.php N... dir settings/.snapshot An error occurred: Stale NFS file handle (116) in waa__build_tree: chdir(hourly.5) Apparently "fsvs" hammered the NFS mounted folders so hard that something went wrong. The NFS server is a NetApp, that is supposed to be rock solid. Even the backup agent, or the "tar cvzf extension.tar.gz ./extension" command why run periodically do not wreck the NFS folders. My questions are: - why did the fsvs commands "sync-repos" and / or "status" scan the 2 NFS folders even though I added them to the ignore list? Is it by design? - I don't know why some NFS folders appear to be wrecked on the client machine (even though nothing is wrong with their content, that I can read from SERVER1 correctly), but is there a way to "slow fsvs down" so that it does not pound on the filesystem too hard? I'm using FSVS 1.1.17 on RHEL4. Regards Farzad FARID 2008-11-26T18:09:06 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/634 Hi Phil, my gratulation to release of version of fsvs 1.1.17 I know its hard work to satisfy every user request. I hope this release is a step closer to close the small gaps. For me this is the .subversion folder creation using native fsvs. Currently I still go with the password patches which allow me too use a static password. On last check at http://fsvs.tigris.org I saw that a lot of links to documentation got lost. Is this because of major upgrade of tigris page? IMO a lot of (new) users would profit from getting access to documentation. I am just playing with the new directory ignore feature which when I understand correctly has a big use for /etc/fsvs because I can specify explicit files to monitor but not the fsvs folder itself, is that right? We just recognized a blocking behaviour on debian/ubuntu systems related to base-files package upgrade. The package uses find to check the /etc folder for symlinks (dont know the exact reason,yet) and loops through the fsvs folder, crying when finding a already checked symlink in /etc/fsvs folder. quick workaround: better workaround: ? Best wishes, Gunnar Gunnar Thielebein 2008-11-25T14:30:34 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/633 Hello everybody! For multi-URL operation it's useful to have a shortcut for switching the URL an entry belongs to; that means that at the old URL the entry gets removed, and added again at the "new" URL. Now there's a "switch" command in svn - but that means "switch a whole working copy to another URL", and I'm not sure whether that's a bad association one could build - since "svn switch" changes the local working copy, but this "fsvs switch" would change the repository data. I'd like to ask about suggestions how to name that command ... "switch" would match nicely, apart from the collision above. Ideas? And BTW: has somebody already looked at the auto-props? Regards, Phil Philipp Marek 2008-11-25T07:27:17 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/631 Hello everybody! For real heroes there's a first version of the auto-prop feature on trunk; and I even include the manual page and HTML file here, so that interested people can play around a bit. Please test - and provide some feedback, so that I can cut another release soon. (Of course, it's entirely possible that trunk eats your root filesystem for lunch, and your backup in the evening ... yeah, it takes real heroes ;-) Regards, Phil Philipp Marek 2008-11-19T07:22:19 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/629 Hi, FSVS 1.1.7 work rather well now, but I have 2 issues related to a rather peculiar setup. As the next version add some features, especially regarding exclusions, I first want to know if these will solve my problems or not. The infrastructure I'm working on use an NFS server and a pool of web servers that mount the same NFS volumes. The application directory under FSVS control contains 2 NFS mounted subdirectories. * Read-only subdirectories On some servers (front office), the NFS volumes are mounted readonly. Although I was able to setup FSVS correctly the first time. Now that some files have been updated on the back office server (mounting the same volumes in R/W mode) I can't update the fsvs config anymore: ------------------------------------ root< at >frontend1]# fsvs update Updating svn://10.10.3.24/xxxxx to revision 193. An error occurred: Read-only file system (30) in up__set_meta_data: utimes(./settings/siteaccess/admin/content.ini.append.php) ----------------------------------- How can I solve this? I'd say the best solution is to "fsvs ignore" the R/O subfolders on the servers, but is there another solution? * Subtle time differences between servers On the backend servers, the NFS volumes are mounted R/W. - I commited the changes on "backend1" with "fsvs commit". - I try to update "backend2" with "fsvs update" Unfortunately, for the shared folders, FSVS finds that on backend2 some files have had their modification time modified, which is of course not the case. Even if I try to "fsvs revert" the guilty files, they always appear as being locally modified and "fsvs update" refuses to run. Again, is there a solution other than ignoring the shared folders on one of the backends, and thus versionning them on "backend1" only? Regards Farzad FARID 2008-11-18T17:07:30 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/618 Hi, As I'm currently deploying FSVS for my customer, I immediatly repackaged version 1.1.17 and installed it on a server I just configured yesterday (I had just run "fsvs urls", "fsvs ignore", and commited nothing yet with fsvs 1.1.16). Here are the problems I have: * config_dir does not seem to work. I added "config_dir=/root/.subversion" to "/etc/fsvs/182f153bd94803955c2043e6f2581d5d/config", but it is not recognized! FSVS keept asking me for root's password. Then I created the file "/etc/fsvs/config" with the same line, to no avail. So I created a symlink from "/root/.subversion" to "/etc/fsvs/auth", and then it worked. But apparently FSFS does not take the option into account. * I'm blocked by a mysterious error.. I don't know if it is related to version 1.1.17, but now any "commit" or "add" command fails, I can't add anything to my repository. Here is the context: - Versionning "/etc" - 2 URLs: "local" priority 100 and "base" priority 200 - I started by commiting some local files: fsvs commit -o author=farzad.farid -o commit_to=local -m "Premier commit local pour backezp-pp1" hosts postfix sysconfig/network sysconfig/networking sysconfig/network-scripts sysconfig/netdump_id_dsa [ ... etc .... ] fstab adjtime system-info fsvs This worked. - Now I want to commit all the other files to "base". I know the following command would fails, but I wanted to be sure. The "commit_to" option is set to "base": # fsvs commit -o author=farzad.farid -m "First commit of 'base' files" Committing to svn://10.10.3.24/system/preprod/back/trunk/etc ..C. dir sysconfig N... 4765 sysconfig/apmd N... dir sysconfig/apm-scripts N... 12971 sysconfig/apm-scripts/apmscript An error occurred: Name does not refer to a filesystem directory (160016) in ci__directory: editor->close_file: Path 'sysconfig' not present - Ok, now I run the following: # fsvs add sysconfig But get the following error: An error occurred: Unrecognized resolver error (134737156) in main: action add failed And now, every "commit" or "add" commands ends with this "Unrecognized resolver error"! I don't know how to repair this. I even tried to run "fsvs sync-repos", to no avail. Did I do something wrong, or is there a bug? My configuration is: - Red Hat Entreprise Linux 4 update 5 - Subversion 1.5.2 - FSVS 1.1.17 - This setup worked perfectly on 2 other servers and I "versionned" their "/etc" directory using fsvs 1.1.6. BUT, I think at some point I also got this kind of error message with fsvs 1.1.16, but it went away after some fiddling, which I don't remember exactly.. Running "fsvs add", "fsvs sync-repos", adding directories manually with "svn mkdir svn://...../etc/sysconfig", etc. Regards. Farzad FARID 2008-10-29T16:36:40 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/613 Hi, As Phil Marek asked, here are my first impressions on using FSVS (1.1.16) with 2 URLs. I'm versionning "/etc" for the moment. Setting up the first server with 2 SVN URL was a bit tedious, because I had to decide which file/directory would go to "base", and which would go to "local", but this problem is not related to FSVS. Here are the problems I have encountered for the time being: 1) Selecting the right repository the first time The first difficulty comes from moving a file or directory from one repository to another, if the first chosen repository was the wrong one. The best solution I found is the procedure. Lets say for example that "/etc/posftix" was committed in "base" (the common URL/repository), but must actually be local to each server: cd /etc fsvs unversion postfix fsvs commit -m "Moving /etc/postfix from 'base' to 'local', phase 1" -o commit_to=base postfix fsvs commit -m "Moving /etc/postfix from 'base' to 'local', phase 2" -o commit_to=local postfix This does not always work smoothly: if the subdirectories do not exist in the 2nd repository, I have to add them manually first. If for example, I want to move "/etc/sysconfig/network-scripts" from one URL to another, before using the previous procedure I have to execute: fsvs add -o commit_to=local /etc/sysconfig 2) Putting /etc/fsvs in the right repository I'm versionning "/etc", so "/etc/fsvs" MUST be handled by the "local" URL/repository, of course :) That's because each server sharing the common "base" URL/repository must have it's own configuration. I don't think this is mentionned in the Master/Local HOWTO? 3) Handling mixed-repository commits This is the biggest problem I have, I already mentionned this in a previous post. Here is an example: - Lets say I modifiy files belonging to the "base" repository. - As we already know, "/etc/fsvs" (which belongs to the "local" repository), is always in a modified state. - I want to commit the changes to the "base" repository without explicitely giving the names of modified files/directories, because it is tedious (and in somes cases there may be dozens of modified files in multiple subdirectories). - The following command returns an error: [root etc]# fsvs commit -m "Delete modprobe.conf_" Committing to svn://10.10.3.24/system/preprod/front/trunk/etc D... 194 modprobe.conf_ .m.. dir fsvs .m.. dir fsvs/182f153bd94803955c2043e6f2581d5d .mC. 161 fsvs/182f153bd94803955c2043e6f2581d5d/Urls An error occurred: Name does not refer to a filesystem directory (160016) in ci__work: editor->close_edit: Path 'fsvs' not present As Phil explained, it is normal to have an error here, but practically it is very tedious to handle. In this example I just have to use: 'fsvs commit -m "Delete modprobe.conf_" modprobe.conf_', but there are cases where '.' is modified. Therefore I can't commit '.', otherwise it'll recursively commit the whole "/etc". I could prevent this by adding "-N" which says "do not recurse", etc. etc. If the commands to type become too complicated, with special cases, I know that my customer will refuse to use fsvs :( 4) Adding a second server to the common "base" Now that I have 1 server versionned in FSVS, with a common "base" and a "local" repository. I now add his twin brother: another running server, already fully installed and in production. To configure FSVS, I give this 2nd server the common "base", and its own "local" repository. From them on, I had a hard time getting the 2 servers in sync! This is because I did not install the 2nd server from scratch: I had to resolve the differences between the 2 servers by hand. This situation is not FSVS's fault. But I know I had to use "fsvs sync-repos", "fsvs update", "fsvs commit", "fsvs add", "fsvs unversion", "fsvs revert" multiple times, in multiple orders, on *both* servers.. I haven't been able yet to create a reliable checklist on how to add the 2nd server to the FSVS versionning. I remember that, at some point, after I manually solved many conflicting changes, "fsvs update" on the 2nd server did not work! It did'nt update any file. I'm still manually resolving minor conflicts on the 2nd server with "fsvs revert". I takes some time, but it works fine. Using "fsvs status -vC | fgrep - v '......'" was the best solution I could find to list all the changes and determine if they are minor (just a date diffence in most cases) and can be reverted on the 2nd server in order to be in sync with the 1st one. So far nothing broke :) I haven't lost a single file, and installing FSVS even helped me spot oddities, like files which should have been identical on the 2 servers, but were not. 5) Choosing the SVN directory structure My customer and I chose the following tree: /customer_name_N /project_name_M /generic_machine_X /trunk /etc /app /generic_machine_Y /trunk /etc /app /machines /machine_A /trunk /etc /app /machine_B /trunk /etc /app /project_name_M' /.... /customer_name_N' /.... The ".../generic_machine_X" contains the "base" repository for a given class of identical servers. The ".../machines" folder contains the "local" repository of each server. My Suggestions: -------------- - In mixed-repository cases, one solution would be that FSVS checks which files belong to the repository I am committing to, and *ignores* files who don't belong to it. - Another solution would be to have an option to explicitely *exclude* files or directories from a commit command. - My prefered solution is that FSVS uses the information it already has to determine where to commit each file. The "priority" parameter of each URL could resolv conflicts. - What about adding an option to "fsvs status", to display the URL alias of each file/directory? - Finally, in a multiple URL configuration, I find myself using the "-o commit_to=XXXX" very often! It'd be nice to have a shortnamed command line option for this :) Best regards, Farzad FARID 2008-10-27T15:35:29 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/597 Hi, I'm having the following issue with FSFS 1.1.16 and the "/etc" directory I'm versionning: apparently, the "/etc/fsvs/xxxxxxx/Urls" file is modified *after* the "fsvs commit" command has finished. As a result, there are always 2 uncommitted change in my "/etc" folder ;) Here is an example: [/etc] # fsvs status .m.? 51 fsvs/182f153bd94803955c2043e6f2581d5d/Urls .m.. dir fsvs [/etc] # fsvs commit -m "Mise à jour automatique conf fsvs" Committing to file:///usr/local/fsvs-repository .m.. dir fsvs .mC. 51 fsvs/182f153bd94803955c2043e6f2581d5d/Urls committed revision 9 on 2008-10-13T09:28:57.786861Z as root [/etc] # fsvs status .m.? 51 fsvs/182f153bd94803955c2043e6f2581d5d/Urls .m.. dir fsvs Comparing the old and new "Urls" file, I see that the only change is the last revision number. I'm a bit embarrassed, because I wanted to use a cron script to check for uncommitted changes, but 'fsvs commit -o empty_commit=no -m "cron" /etc', as specified in the fsvs-options manpage, would commit this same change over and over :) Is there an elegant solution to my problem, apart from ignoring "/etc/fsvs", which is a solution I don't really like? Regards, Farzad FARID 2008-10-13T13:21:41 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/591 Hi, I am embarassed because I tested fsvs on Debian, but my customer's target distribution is Red Hat Entreprise Linux 4, and by default fsvs can't compile on it... I know it's old but it's my customer's production platform ;) The configure script depends on the "apr-1" library version, RHEL4 only provides "apr-0", and there is a missing "svn_ra_initialize" symbol in "svn_ra-1". Here are the package versions provided by RHEL4: apr-0.9.4-24.5 apr-util-devel-0.9.4-21 apr-devel-0.9.4-24.5 apr-util-0.9.4-21 subversion-1.1.4-2.ent subversion-devel-1.1.4-2.ent Is there a way to compile fsvs on RHEL4 anyway? Regards, Farzad FARID 2008-10-06T15:12:54 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/581 Hi, I setup a test system, using FSVS 1.1.16, with 2 repositories, and one working directory, as follows: WC: /usr/src/FSVS/etc URLs: N:base,P:100,file:///usr/src/FSVS/repos/base/trunk/etc N:local,P:200,file:///usr/src/FSVS/repos/machines/M0379/etc The WC is a copy of my "/etc" directory. Following this howto (http://fsvs- software.org/doc/doxygen-gif/group__howto__master__local.html), I commited some files to the "local" repository, and all the other files to the "base" repository. Now, for example, I modify "/usr/src/FSVS/etc/hostname". If if commit without giving the "commit_to" option, I get an error message: # fsvs commit -m "Touched file" hostname Which URL would you like to commit to? Please choose one (config option "commit_to"). But "hostname" is already in the correct repository: # fsvs info hostname .m.? 16 hostname Type: file URL: file:///usr/src/FSVS/repos/machines/M0379/etc/hostname Status: 0x28 (mtime, likely) Flags: 0x0 (none) Dev: 65024 Inode: 2166935 Mode: 0100644 UID/GID: 0 (root)/0 (root) MTime: Fri Oct 3 16:02:12 2008 CTime: Fri Oct 3 16:02:12 2008 WAA-Path: /var/spool/fsvs/ea/45/33db34f563d21d08b4066d2f4ccf/ Revision: 6 Repos-MD5: 90dc9df7334df5036bd88b3dc3a0055c Size: 16 Moreover, if I set "commit_to=base" in the "config" file, I will get an even worse error message: # fsvs commit -m "Touched file" hostname Committing to file:///usr/src/FSVS/repos/base/trunk/etc .m.. 16 hostname An error occurred: Filesystem has no item (160013) in ci__directory: open_file I thought that FSVS would automatically know where to commit the file, why doesn't this work? Can I use FSVS with 2 URLs without having to use "-o commit_to" and/or with having a conflict if the default "commit_to" is not the one associated with som of the files I want to commit? Shouldn't the priority field play the same role as the default "commit_to" in the config file? Regards, Farzad FARID 2008-10-03T15:14:10 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/577 Hi, Apparently the ignore list is not versionned. When I checkout a copy of a repository, I get an empty ignore list. Will this feature be added to fsvs? Regards, Farzad FARID 2008-10-02T16:06:04 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/576 Hi, I'm testing fsvs 1.1.16 on a Debian system, using the official Debian package. I created one repository, file:///usr/local/fsvs-repository, and committed "/etc" to it. BTW I know I should have created a subfolder on SVN first, but it was my first test install. The corresponding fsvs URL is: # fsvs urls N:,P:0,file:///usr/local/fsvs-repository I played with fsvs a bit and got it working correctly. By reading the manpage (which by the way does not completely describe the URL format, I opened an issue for this), I understood that I could give a name to the URL. So I ran the following command: (echo 'N:main,file:///usr/local/fsvs-repository') | fsvs urls load But it apparently broke fsvs! After the modification, I tried to make a commit: # fsvs commit -m 'Mise à jour de VMware' vmware rc5.d thnuclnt vmware-vix cups xdg init.d rc2.d rc3.d Committing to file:///usr/local/fsvs-repository .m.. dir init.d .mC. 10785 init.d/vmware An error occurred: Transaction is out of date (160028) in ci__directory: open_file "fsvs status" says there are modified files in the repository, but I think I never modified the SVN repos directly... Not knowing if the "transaction" mentionned here has any link with the SVN transaction, I ran "svnadmin lstxns /usr/local/fsvs-repository" but it didn't output anything. I ran "fsvs update" anyway: # fsvs update Updating file:///usr/local/fsvs-repository to revision 6. .mC. 498 fstab .mC. 277 network/interfaces .mC. 3726 network/if-up.d/mountnfs .mC. 261 network/if-up.d/avahi-daemon .mC. 32 network/if-up.d/wpasupplicant [... many more lines ...] .mC. 4546 init.d/dbus .mC. 1773 init.d/dirmngr .mC. 4521 init.d/hwclock.sh The entry ./init.d/vmware has changed locally But it doesn't modify anything. and "fsvs commit" still doesn't work. I tried undoing my urls change by running: (echo 'N:,file:///usr/local/fsvs-repository') | fsvs urls load But nothing changes. I have the same error messages. Can someone help me and tell me what went wrong? And how can I fix the repository without destroying and recreating it, which would make me loose the log history? Regards, Farzad FARID 2008-10-02T14:14:41 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/569 I have a strange behaviour in fsvs. When I perform fsvs st on some machine i get this output: this was formerly as ..C. but i did unversion (.) from / folder. I assume that me or someother did accidently a commit from another directory. Unfortunately i dont see which directory was originally included. At all i cant get this one committed the (.) resides on fsvs status. when doing fsvs sync-repos it gets stucked at this entry (.) ...someoutput (etc is originally included) Gunnar Thielebein 2008-10-01T10:16:24 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/564 First, isn't it a good idea? I just want to (try to) commit /etc changes every night. I put fsvs commit -m 'nightly commit' in a cron.daily script; but from what I can tell it fails on authentification. I can't find anything on how to specify login/password on the command line; help appreciated. NM 2008-09-29T12:49:43 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/560 Hi, When an "fsvs up" aborts after having updated a few files already, those files are marked as changed. The next "fsvs up" will fail with: The entry ... has changed locally. (where ... is one of the updated files). When asked for the differences, fsvs will show the differences between the updated file and the previous revision from the archive (the revision at which the work area was before the aborted update I suppose). What I can't figure out though is why it aborts the original update. Here's a sample session (alias status="fsvs -C -f text,owner,group,mode"): griffon26< at >griffon26 ~> status D... 905 .irssi/friends.backup .mC. 1333 .irssi/friends .mC. dir .irssi N... 15360 .fetchids N... 10 .fetchmail.pid .mC. dir . griffon26< at >griffon26 ~> fsvs up Updating svn+ssh://10.0.0.2/home/griffon26/repos/fsvsrepo/home-base to revision 19. .mC. 47 .ssh/config .m.. dir .ssh .mC. 96 .unison/webdefault.prf .mC. 111 .unison/default.prf .mC. 206 .unison/mail.prf .m.. dir .unison The entry ./.fsvs has changed locally griffon26< at >griffon26 ~> status .mC. 96 .unison/webdefault.prf .mC. 47 .ssh/config .mC. 111 .unison/default.prf .mC. 206 .unison/mail.prf .m.. dir .unison .m.. dir .ssh D... 905 .irssi/friends.backup .mC. 1333 .irssi/friends .mC. dir .irssi N... 15360 .fetchids N... 10 .fetchmail.pid .mC. dir . griffon26< at >griffon26 ~> fsvs revert .ssh/config .unison/ Reverting to revision 18: .mC. 110 .unison/webdefault.prf .mC. 48 .ssh/config .mC. 86 .unison/default.prf .mC. 190 .unison/mail.prf .m.? dir .unison/ griffon26< at >griffon26 ~> status D... 905 .irssi/friends.backup .mC. 1333 .irssi/friends .mC. dir .irssi N... 15360 .fetchids N... 10 .fetchmail.pid ..C. dir . 20 goto 10 ;-) This is revision 1881 from svn, but my metadata may be from an older version. Regards, Maurice. Maurice van der Pot 2008-09-17T20:46:36 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/554 Hi I will backup my image files (jpg an raw) with fsvs. The space of this files is about 80 GB of data. If I start the commit with "fsvs commit -m 'Initial' " I get an out of space error in my /tmp directory. fsvs created many files in this dir with names like fsvs.0gwNu9, fsvs0m67tG an so on. The free space on tmp is 1 GB so if I commit the image files it runs in out of sape on /tmp after 1 GB of data. On the svnrepo server I have 200 GB free space so check in the 80 GB of data must be posible. Now my question is there any way to prevent fsvs from creating this many tmp files. If not you nead the same amount of space on tmp to commit an data directory tree. I have noting found in the documentation or on the web about this tmp files of fsvs. Thanke you for any help. Roland rsl 2008-09-08T17:55:52 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/540 Ladies and Gentlemen, We have a unique challenge that we're trying to address using fsvs. We have a lot of servers out "in the wild" as it were, and instead of using some sort of package management system to upgrade the OS and our own software, we want to use fsvs. The idea is that we can make updates on our own master server, check them into fsvs/subversion, and then have each of the "in the wild" servers update from fsvs/subversion. This seems like a great idea, but we've had a bit of difficulty when trying to actually get these updates to work. In our testing environment, we'll make some changes and then commit them fine, but when we try to do an update, we will often (but not always) get something like the following: dev-01 / # fsvs update -r 19 Updating svn+ssh://user< at >svnserver//home/user/svn/osrepo to revision 19. The entry ./etc/fsvs has changed locally We've tried with and without the "-r <revision>", and we don't always get the same file as having changed (though it is usually one of a handful of files). I'm fairly certain that the file in question has not in fact changed. One thing we've tried is doing a revert just before an update, but that doesn't seem to fix it. We really like fsvs, from a conceptual level, and it seems like the right solution, but this has us pulling our hair out. Can anyone shine any light on the situation? Is this an imporper use of this package? Are we missing something obvious? I can elaborate on our setup and such, if that would be helpful, but I don't want to dump a bunch of configs on this list if it isn't necessary. Thanks in advance for any insight you can offer, Stu Stuart Lester 2008-08-26T17:32:01 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/527 Hi all. 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. Here my ignore list: ./media/*/** ./mnt/*/** ./proc/** ./sys/** Everything else is included: /dev, /var/run, /var/lock Here my commits log: ------------------------------------------------------------------------ r87 | root | 2008-08-14T08:19:51.031668Z | 1 line backup 2008-08-14 aptitude clean ------------------------------------------------------------------------ r86 | root | 2008-08-14T08:18:08.803716Z | 1 line backup 2008-08-14 aptitude autoclean ------------------------------------------------------------------------ r85 | root | 2008-08-14T08:13:44.560284Z | 1 line update 2008-08-14 VirtualBox (1.6.4) ------------------------------------------------------------------------ r84 | root | 2008-08-11T08:47:45.485636Z | 1 line backup 2008-08-11 Thunderbird (email accounts) ------------------------------------------------------------------------ I want to revert revision 85 Or I want to update to revision 84 1) 'sudo fsvs update -r 84' failed with msg "permissions denied" - it try to update directory /dev and it failed. 2) 'sudo fsvs export -r 84' failed with msg "killed" - I am not sure but I think it means "out of memory" 3.1) 'sudo fsvs revert -r 85 -R -CC /' - failed, again problems with directory '/dev'. 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. 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. So... what are my mistakes? 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. 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. Today I got some different errors (I am using ubuntu gutsy): 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). 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')). Again I got error: ....... What to do? Any comments are welcome (plus I am online in IRC #fsvs). Thank you in advance. Plamen. MMM MMM 2008-08-18T12:30:58 http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/502 Hi Philipp and others, (To refresh your memory) I'm using fsvs to keep files in my homedir under version management using this: export FSVS_SOFTROOT=${HOME} export FSVS_CONF=${FSVS_SOFTROOT}/.fsvs export FSVS_WAA=${FSVS_CONF}/waa I have two machines that do this. Tonight I noticed that the changes to the ignore list are not being committed. Here's a sample session. (status is an alias for fsvs -C -f text,owner,group,mode commit is an alias for fsvs ci -o empty_commit=no -C -f text,owner,group,mode) griffon26< at >griffon27 ~> status .mC. 975 .fluxbox/keys .mC. 6857 .fluxbox/init N... 48 .ssh/config .mC. dir .ssh N... 1180 bin/mailwatch.sh .mC. dir bin .mC. 1328 .xsession .mC. 1129 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign N... 48 .cvsrc N... dir public_html_shared .mC. dir . griffon26< at >griffon27 ~> commit Committing to svn+ssh://localhost/home/griffon26/repos/fsvsrepo/home-base .mC. dir .ssh N... 48 .ssh/config .mC. dir bin N... 1180 bin/mailwatch.sh .mC. 1328 .xsession N... 48 .cvsrc N... dir public_html_shared committed revision 12 on 2008-08-08T21:28:03.627076Z as griffon26 griffon26< at >griffon27 ~> fsvs .m.. dir .fsvs/6666cd76f96956469e7be39d750cc7d9 .m.. dir .fsvs griffon26< at >griffon27 ~> status griffon26< at >griffon27 ~> md5sum .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign 8755e0a3395d074aa2451b326645ff04 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign griffon26< at >griffon27 ~> On the other machine: griffon26< at >griffon26 ~> fsvs up Updating svn+ssh://10.0.0.2/home/griffon26/repos/fsvsrepo/home-base to revision 12. N... 48 .ssh/config .mC. dir .ssh .mC. 1328 .xsession N... 1180 bin/mailwatch.sh .mC. dir bin N... dir public_html_shared N... 48 .cvsrc ..C. dir . griffon26< at >griffon26 ~> md5sum .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign 8b2c297da63b650766423f6736c76093 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign griffon26< at >griffon26 ~> Any idea what's going on here? Regards, Maurice. Maurice van der Pot 2008-08-08T21:36:49 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.sysutils.backup.fsvs.general