dump-users

[Dump-users] Verify with -Mf stalls asking for next tape

[Kenneth P. <sh...@se...>]

I'm doing a multi-file dump (-B 1000000 -Mf) to an external USB drive. I 
then do a verify (restore -C) to check the backup. My last verify stopped 
with this prompt:

You have read volumes: 2, 3, 4, 5, 6
Specify next volume # (none if no more volumes): 7
resync restore, skipped 230 blocks

Normally I run this from a script at midnight Saturday, so the prompt fails 
the backup with no input. Here I ran the verify by hand from a shell window 
and was able to let it continue by entering the next file number.

It would be nice if the operation would continue without prompting in this 
situation, reading until no more files were available.

What would cause restore with -Mf to prompt like this?

BLOCKING=64
MAXMISCOMPARES=10000
SIZE=1000000
DUMPSUBDIR=/mnt/Backup/0

$DUMP 0u -h 0 -b $BLOCKING  -Mf $DUMPSUBDIR/root/dump \
 -Q $DUMPSUBDIR/root/qfa -B $SIZE /

/bin/mount -o remount,noatime /
$RESTORE -C -l -L $MAXMISCOMPARES -b $BLOCKING -Mf $DUMPSUBDIR/root/dump
/bin/mount -o remount,atime /

Re: [Dump-users] Verify with -Mf stalls asking for next tape

[Stelian P. <st...@po...>]

Le mardi 11 mars 2008 à 15:24 -0700, Kenneth Porter a écrit :
> I'm doing a multi-file dump (-B 1000000 -Mf) to an external USB drive. I 
> then do a verify (restore -C) to check the backup. My last verify stopped 
> with this prompt:
> 
> You have read volumes: 2, 3, 4, 5, 6
> Specify next volume # (none if no more volumes): 7
> resync restore, skipped 230 blocks
> 
> Normally I run this from a script at midnight Saturday, so the prompt fails 
> the backup with no input. 

Do you mean that you get prompted for the next volume number each
night ?

> Here I ran the verify by hand from a shell window 
> and was able to let it continue by entering the next file number.
> 
> It would be nice if the operation would continue without prompting in this 
> situation, reading until no more files were available.

Well, it is supposed to work this way when -M is used...

-- 
Stelian Pop <st...@po...>

Re: [Dump-users] Verify with -Mf stalls asking for next tape

[Kenneth P. <sh...@se...>]

On Wednesday, March 12, 2008 10:44 PM +0100 Stelian Pop 
<st...@po...> wrote:

> Well, it is supposed to work this way when -M is used..

I added -a and it now runs without the prompt.

Re: [Dump-users] Verify with -Mf stalls asking for next tape

[Stelian P. <st...@po...>]

Le mercredi 12 mars 2008 à 16:52 -0700, Kenneth Porter a écrit :
> On Wednesday, March 12, 2008 10:44 PM +0100 Stelian Pop 
> <st...@po...> wrote:
> 
> > Well, it is supposed to work this way when -M is used..
> 
> I added -a and it now runs without the prompt.

Hmm, the only place where it does matter is in tape.c:

>	if (aflag || curfile.action != SKIP) {
>		... do not ask for volume number ...

Normally, curfile.action is never SKIP when comparing, since all the
files are extracted and compared with the original ones.

The only cause I can think of is that you had an earlier comparision
error causing the current file to be skipped instead of comparing, and
this is why curfile.action == SKIP. Did restore report some compare
errors before asking for the next volume ?

-- 
Stelian Pop <st...@po...>

Re: [Dump-users] Verify with -Mf stalls asking for next tape

[Kenneth P. <sh...@se...>]

--On Thursday, March 13, 2008 12:49 PM +0100 Stelian Pop 
<st...@po...> wrote:

> The only cause I can think of is that you had an earlier comparision
> error causing the current file to be skipped instead of comparing, and
> this is why curfile.action == SKIP. Did restore report some compare
> errors before asking for the next volume ?

I think so. I suspect tmpwatch ran between the backup and verify, and so a 
file in /tmp was missing that had been backed up just at the end of one of 
the multi-files. Here's what I'm seeing:

/sbin/restore: unable to stat ./tmp/Transfer.h: No such file or directory
/sbin/restore: unable to stat ./tmp/rstdir1204185728-iRW4Q2: No such file 
or directory
/sbin/restore: unable to stat ./tmp/rstmode1204185728-iixqxV: No such file 
or directory
You have read volumes: 2, 3, 4, 5, 6
Specify next volume # (none if no more volumes): Dump   date: Sun Mar  9 
00:17:08 2008

(I should add /tmp to the exclude list with chattr. But I can see this 
happening with other files.)