From: Sylvain Robitaille (syl@alcor.concordia.ca)
Date: Tue Nov 05 2002 - 16:50:02 EST
[ This message posted to the comp.unix.tru64 newsgroup and mailed to the
tru64-unix-managers and unix-wizards mailing lists. My apologies to
those who will see it multiple times... ]
On Mon, 4 Nov 2002, I wrote:
> What this says, though about my ability to recover a 5.1A system in the
> event of disaster is frankly quite depressing. :-(
After further investigation, I've found that the cause of the problem
was in how my backup/recovery application deals with sparse (and
"apparently sparse?") files. In fact, I was able to *copy* the reloaded
kernel back onto itself, as follows, and finally boot correctly:
mv /mnt/vmunix /mnt/vmunix.20021105
cp -p /mnt/vmunix.20021105 /mnt/vmunix
I can adjust my backup software to not pay particular attention to the
"sparseness" of files in the root partition, and that should result in
reloadable backups.
Once again, thanks to all who sent in comments and suggestions. This
seems like it should have been much simpler to resolve than it was...
-- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ----------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:58 EDT