Path: utzoo!utgpu!water!watmath!uunet!lll-winken!lll-tis!pacbell!att-ih!ihnp4!ihopa!ihop3!ihtlt!kosman!kevin
From: kevin@kosman.UUCP (Kevin O'Gorman)
Newsgroups: unix-pc.general
Subject: Re: Restoring a tape backup after a crash
Summary: Further ruminations on this process
Message-ID: <366@kosman.UUCP>
Date: 14 Apr 88 22:54:52 GMT
References: <365@kosman.UUCP>
Organization: K.O.'s Manor - Vital Computer Systems, Oxnard, CA 93035
Lines: 15


Some other observations about this restore process (see my last article).

The restore process for some reason NEVER restores the modification dates.
I now wish I had changed /usr/bin/Trestore.sh to have the -m flag in the
tapecpio command before I did the restore.  EVERYTHING now has today's
date.

When I rebooted after the restore, I was worried that the system rebooted
itself after doing the file system check.  Then I thought about it and stopped
worrying.  There's a comment in /etc/profile.hd which bears on this: some of
the files (/lib/shlib, /dev/console, and some others) are open when the restore
is happening, and restoring onto them seems to do something funny to the inode
reference counts which fsck has to clean up.  This used to happen with the
Foundation Set, too, until AT&T figured out the fix.  Looks like more trouble
than I want to worry about unless there's a big reason to worry.