|
From: Stelian P. <st...@po...> - 2011-05-24 18:07:01
|
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...> |