Date: Tue, 31 Mar 1998 10:53:31 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> Cc: current@FreeBSD.ORG Subject: Re: CONTINUED problems: Restore/Dump broken? Message-ID: <XFMail.980331105314.shimon@simon-shapiro.org> In-Reply-To: <199803311826.LAA05074@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31-Mar-98 Justin T. Gibbs wrote: ... > I don't seem to have this problem with dump and restore here. In testing > out the "new" CAM tape driver, we've made several dumps and restores > using > blocksizes much larger than 512bytes. These were usually performed to > either an Archive Python DDS-2 drive or an Exabyte Eliant drive. This is in the current current. Not in CAM. We still have to use it until we all convert to CAM, CAM is in the main branch, etc. > One thing that could be biting you though is that dump defaults to a > 10k block size while restore will default to a 32k block size. I haven't > analyzed the source enough to see if it will properly handle cases where > the blocksize is smaller than the default. I always explicitly specify > the blocksize. As I said before, this happens with cpio too. You do: cd /etc;find . | cpio -H newc -ov -C 65536 -O /dev/nst2.2 then you do: cpio -H newc -ivt -I /dev/nst2.2 -C whatever_you_want And you will get garbage out. In my innocense I assume that the blocking factor to the tape, and the logical blocking of an application can/should be decoupled. It appears that a) they are not, and b) anything other than 512 bytes breaks. Now, this DID work correctly up to some months ago. I checked it, under -current very carefully. since you get NO INDICATION of failure when you WRITE the tapes, there was no reason for me (and others) to check again. Maybe it is busted only with the Sony. Maybe not. I'll put an HP drive on one of the systems here today and see what it does. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980331105314.shimon>