Paul Lussier wrote:
In a message dated: Mon, 26 Nov 2001 22:58:35 +0100
Bernhard R. Erdmann said:
Doublecheck /etc/fstab for this entry. Dump gets the corresponding block
device to the filesystem in the disklist by looking at /etc/fstab.
Hmmm, does that mean that if there's not an
In a message dated: Mon, 26 Nov 2001 22:58:35 +0100
Bernhard R. Erdmann said:
Doublecheck /etc/fstab for this entry. Dump gets the corresponding block
device to the filesystem in the disklist by looking at /etc/fstab.
Hmmm, does that mean that if there's not an fstab entry that there
will be
These dumps were to tape Datapark08.
Tonight's dumps should go onto 1 tape: Datapark10.
...
so the tape for tonight instead of 09, it jumps to 10. And this is
happening quite often lately so I can't predict which tape to go in next
and have to rely on the report. ...
Your tapelist file
Hi Oliver,
That is what I thought too. However, the tape number jump to
different number of tape instead of the usual. For instance, in this case
in the report:
===
These dumps were to tape Datapark08.
Tonight's dumps should go onto 1 tape: Datapark10.
===
so the tape for tonight instead of 09, it jumps to 10. And this is
happening quite often lately so I can't predict which tape to go in next
and have to rely on the report. So I guess my question would be is there a
way to by pass certain directories, eg. the mail queue, ?
Tape order and
? gtar: Cannot add file ./var/spool/mqueue/xfMAA07342: No such file or
directory
| Total bytes written: 2192885760
When tar builkd the directory, the file was present, when it came to
back-up the file, it was not anymore, the mail had been sent and
removed from the queu.
It is normal, just a
Hi All,
I am very new to this. So if the question I ask has been answered before,
please bare with me and point me to the right direction.
My problem is a strange dump error which seemed to occur more and more
often. I think I know what the problem is but not know how to fix
