Hello,
I replying to share with you, what I found out with this problem. Thanks to
the one who replyed to me. Well, it took a while for me to find out the
following:
With solaris 8 you can have a mount opption logging (See the mount_ufs man
page). With this I get the error described below. With
Hi,
thanks for the answer.
I expected something like this, but unfortunatelly the image is not split
into multiple chunks on the holding disk and also with amrestore I get the
same message. Amdump runs without error and creates only one image per
partition. Even worse I do have the same entry
... I'm able to restore
all other partitions on that host. When I run amdump again I get the same
result restoring that host but sometimes with a different partition.
Since you mentioned ufsrestore, are you running on Solaris? I have a
vague memory from quite a while ago about this problem and
Here's what I found in a letter from Aug-1999:
What OS? If it's Solaris, this is a known ufsrestore bug I've reported
and Sun has ignored.
In any case, some (buggy) restore programs just seem to get confused when
reading from a pipe. I looked through the old E-mail I have and didn't
I'm trying to restore from the holding disk, after I mounted the directory
from the backup server. I use the following command:
dd if=/a/20010515/volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 | ufsrestore -ifv -
After entering the command, the ufsrestore runs fine for a while. Then I get
the
