I am experimenting with fslint's "findup" script as an alternative for the
non-debian freedups.pl script, which no longer seems to work with Etch, at least
on my system. The findup documentation is sparse or non-existent and I am not
sure I am using it correctly by running directly, but the comments seem to imply
that it should be possible. Prior to the failures, I get some errors due to
md5sum's new method of dealing with backslashes by doubling them in the path
names, but I have no evidence that that is related to the other problem.
I have tried three times to run findup on a 40G backup archive, containing
numerous hardlinks, using the -m option (merge duplicates using hardlinks).
Each attempt has failed. On the first attempt X crashed, followed by two
apparent system "hangs" during subsequent attemps. Each failure occurred after
about 10 hours. Only during the first run, when X crashed, did it report
merging any duplicates. It may have completed the hardlink merges before the
failure, but I have no easy way to confirm that.
After the X crash, the display manager restarted X and the system seemed to run
normally. After the "hangs" occurred, I could ping the system from the LAN, but
could not log in using ssh. All disk activity seemed to stop, although I did
not verify that. After rebooting, no error messages appear in the systems logs.
Based on these observations, I suspect that either the root partition became
inaccessible, or else the CPU was too busy to respond to interactive commands,
causing an apparent hang. (The backup archive is not in the root partition.)
My system is 100% Etch except for an upstream lirc driver. I don't think I have
the time or experience to pursue it much further, and I appreciate any help.
PS: If it turns out to be real and not a "PEBKAC," it will be my first confirmed
Debian (stable) hang. :-(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
