[merge] errors in deleting obsolete packs should not be fatal (was Re: Problems with NFS mounted filestore)

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
| On Tue, May 27, 2008 at 5:27 PM, Russel Winder
| <russel.winder at concertant.com> wrote:
|> I took a new branch of the BzrDev branch and applied the above. patch
|> and tried to get the branch.  Attached is the terminal output
|> and .bzr.log file.
|
| Thanks very much for measuring this.
|
| So it looks like that file is not still in use by this process, and it
| really is just an nfs glitch, about which we can probably do nothing.
| My somewhat rusty memory is that these files just occur and we need to
| ignore them.  How would people feel about silently ignoring them?
|
| There is some risk then that a large number of them would accumulate,
| but that is really an NFS server administration issue generally, not
| our problem.
|

I would start with a warning, and if people complain (it warns too much,
wondering what is going on, etc) then we can silence it.

At least, that is my first response. It sort of depends what the noise levels
would be. If Russel was seeing them *every* time he pushes, then we should just
be quiet about it.

We *should* be the only one putting things into that directory. And we don't
name our pack files .nfs*. We could arguably be whitelisting what we delete from
that directory. Something like: "[a-z0-9]{32}\.(pack|iix|rix|tix|six)"

So *if* we see these warnings a lot, we can just be silent as they are noise
that distracts the user and hides real warnings. If they are only occasional, it
might indicate a problem with nfs.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkg8FJEACgkQJdeBCYSNAAOQYgCfaAyhujIPBQ9BiydJDV9IKbzg
oq0AnAxCKL6/3oqkgZpsq/gtRgQ+34eL
=MVxl
-----END PGP SIGNATURE-----