dump-devel

[Dump-devel] dump | restore SIGPIPE

[Phillip S. <ps...@cf...>]

When running dump | restore, dump gets a SIGPIPE at the end and aborts. 
  I think the correct fix is to make sure that restore continues to read 
from the pipe until EOF ( still looking in the code for that ).  I guess 
that right now restore stops and exits when it sees the end of tape 
record or maybe when it gets the final inode.  Would this be correct, 
and does anyone have a hint about where that fix is needed?

Re: [Dump-devel] dump | restore SIGPIPE

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

On Fri, May 20, 2011 at 11:44:59AM -0400, Phillip Susi wrote:

> Did you intend to take this off list for some reason?

No, sorry, MUA error. Adding back the CC:

> On 5/20/2011 6:00 AM, Stelian Pop wrote:
> >On Tue, May 10, 2011 at 10:01:02AM -0400, Phillip Susi wrote:
> >
> >>When running dump | restore, dump gets a SIGPIPE at the end and aborts.
> >
> >Can you post a log of this problem, because it works fine for me.
> 
> root@iridev-svr1:/mnt# dump -0 -b 1024 -f - /dev/vg0/snap | restore -r -f -

Ok, so this is not a problem with dump | restore, but with
dump -b 1024 | restore.

If you change the default blocksize in dump, you should do the
same in restore. You'll find out that dump -b 1024 | restore -b 1024
works fine.

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

Re: [Dump-devel] dump | restore SIGPIPE

[Phillip S. <ps...@cf...>]

On 5/23/2011 4:26 AM, Stelian Pop wrote:
> Ok, so this is not a problem with dump | restore, but with
> dump -b 1024 | restore.
>
> If you change the default blocksize in dump, you should do the
> same in restore. You'll find out that dump -b 1024 | restore -b 1024
> works fine.

I thought that restore was supposed to automatically detect the block size?

Re: [Dump-devel] dump | restore SIGPIPE

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

On Tue, May 24, 2011 at 10:16:44AM -0400, Phillip Susi wrote:

> On 5/23/2011 4:26 AM, Stelian Pop wrote:
> >Ok, so this is not a problem with dump | restore, but with
> >dump -b 1024 | restore.
> >
> >If you change the default blocksize in dump, you should do the
> >same in restore. You'll find out that dump -b 1024 | restore -b 1024
> >works fine.
> 
> I thought that restore was supposed to automatically detect the block size?

Well, the man page states:
	"If the -b option is not specified, restore tries to determine
	the media block size dynamically."

Emphasise on "tries".

In fact, the "original" (read: cross-platform, BSD compatible)
dump format does not have the blocksize information in the header.
Linux' dump does have it, but it was added along with the compression
abilities, this is why the blocksize information from the header
is only used when the dump is compressed.

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