Hello Farzad!
On Tuesday 18 November 2008 Farzad FARID wrote:
> 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:
...
> 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?
Well, of course FSVS can't change files on an read-only mount.
To get it "know" the last (current) version, you can use "sync-repos" - which
just fetches a new entry list from the repository, as reference point to
compare the WC against.
> * 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?
That I can't explain ...
FSVS keeps timestamps in 1 second steps; so if the filesystem has a 2 second
granularity (like FAT), it might have this problem. But I don't think that
you're using FAT ;-)
Please show me
ls -la --full-time <filename>
and
fsvs info <filename>
Or, wait a second ... if the directories you call "shared" are mounted on both
servers, is the problem (maybe) that backend1 commits changes, but backend2
sees only the modified files but doesn't know about the commit, so refuses to
update?
If that's your problem, you could either
- *read* the documentation for sync-repos, and use that, *if* the only problem
is FSVS' knowledge about the WC state, or
- put the WAA and CONF area on NFS too, so that the shared directories have
this information shared, too,
- or, if the WCs are really different things and the timestamps are just wrong
(different), you could try
fsvs update -o conflict=remote
Hope that helps; but I don't think I really understand your setup, and
therefore the problem, yet.
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]
