Today we had to restore our root directory on DU 3.2C
It's an ADVFS file system and we used the command,
vrestore -iv
It worked fine until the root file system filled up and there wasn't
enough room for temporary files to complete the restore. Investigating
showed a heap of files named like 00134 ... 00296 ... Deleting these
from another session before answering "n" not to abort the restore
allowed things to be restored OK. I imagine if we'd linked /tmp
to another filesystem with enough free space before restoring things
may have gone fine. But where do these files come from?
I suspect they were in /proc when vdump ran. We tried the restore
again excluding /proc from the list of files to restore but the
result was the same. ls in vrestore didn't list them.
The vdump command was,
/sbin/vdump -0 -u -N -f /dev/nrmt0h /
Here's an extract of the vdump log,
vdump: Dumping regular files
vdump: unable to read file <./proc/00000>; [22] Invalid argument
vdump: unable to read file <./proc/00001>; [22] Invalid argument
vdump: unable to read file <./proc/00003>; [22] Invalid argument
vdump: unable to read file <./proc/00025>; [22] Invalid argument
vdump: unable to read file <./proc/00134>; [22] Invalid argument
vdump: unable to read file <./proc/00137>; [22] Invalid argument
vdump: unable to read file <./proc/00189>; [22] Invalid argument
vdump: unable to read file <./proc/00234>; [22] Invalid argument
...
QUESTIONS
How do we exclude these files during the vdump of the / file systems?
Failing this, how do we stop them from being restored to / during
vrestore?
+---------------------------------------------------------------------+
| John Miller | Internet Mail - John.Miller_at_jcu.edu.au |
| Computer Centre |
| James Cook University of North Queensland | Phone: +61 77 815447 |
| Townsville, 4811, AUSTRALIA | Fax: +61 77 815230 |
+---------------------------------------------------------------------+
Received on Fri Aug 01 1997 - 08:59:38 NZST