Many thanks to those who took the time to reply:
George Guethlein <GGuethlein_at_GiantOfMaryland.com>
Trevor Stott <trevor.stott_at_sheridanc.on.ca>
alan_at_nabeth.cxo.dec.com
"Robert L. McMillin" <rlm_at_syseca-us.com>
The resposes varied in solution. Original post included below. I'll go
with either Robert's suggestion of changing partition sizes (since the
disks are not identical anyway, or the response from Alan:
restoresymtable is used by restore to keep track of what
files need to added and/or removed at each application of
an incremental. What I would try is to make a symbolic
link of that name to /tmp or /var/tmp. Create the file
at the other end and then do the restore of the full. If
it asks go ahead and let it overwrite restoresymtable.
Since it just another file, restore shouldn't care where
it really is.
On a new disk, if all filesystems are going to be near full, can use the
future swap partition for a temp FS to hold the restoresymtable. This
seems like it should work.
Once again, the list comes through.
> Hi group,
> It seems to me that this problem must have been solved already, but I
> can't find where. We are trying to "clone" an OS disk for Digital UNIX
> 3.2g. It's not quite a clone, because the drives are from different
> manufacturers, and the block count is not identical. I'd like to use
> dump/restore to copy the filesystems, but the problem is that with a
> near
> full filesystem, the restoresymtable takes all the extra space, and the
> restore fails. I have incrementals to restore after the level 0. Any
> ideas
> of how to handle this? Can I redirect to restoresymtable? Can I link it
> to
> /dev/null, or will this kill the incrementals?
> Any help will be greatly appreciated.
--
==============================================================================
David R. Courtade
System Administrator
Amherst Systems Inc.
30 Wilson Rd.
Buffalo, N.Y. 14221
Phone: (716)631-0610
FAX: (716)631-0629
Email: drc_at_amherst.com
Received on Thu Jan 29 1998 - 12:39:37 NZDT