Date: Mon, 17 Jun 1996 15:23:30 +0200 (MET DST) From: "Georg-W. Koltermann" <gwk@racer.dkrz.de> To: gpalmer@FreeBSD.ORG Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1320: dump limits blocksize to 32K Message-ID: <199606171323.PAA18629@racer.dkrz.de> In-Reply-To: <199606130850.BAA05897@freefall.freebsd.org> (gpalmer@FreeBSD.ORG)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> ""Gary" == "Gary Palmer" <gpalmer@FreeBSD.ORG> writes:
"Gary> The following reply was made to PR bin/1320; it has been
"Gary> noted by GNATS. From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
"Gary> To: gena@netvision.net.il Cc:
"Gary> FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/1320:
"Gary> dump limits blocksize to 32K Date: Thu, 13 Jun 1996
"Gary> 09:42:36 +0100
"Gary>
"Gary> gena@netvision.net.il wrote in message ID
"Gary> <199606130916.LAA16644@Burka.NetVision.net.il>:
>> All this may be true (?) for local backup , but absolutely not
>> when using rdump. I back up my system on DLT SCSI tape
>> connected to Solaris system and tape's manuall says that
>> blocksize = 126 should be spcified.
"Gary> Your patch is wrong for just that reason ... it is true
"Gary> for local backups, and removing the code which does the
"Gary> check is hence incorrect. It should only ignore the
"Gary> blocksize for non-local backups, not ignore it totally.
"Gary>
"Gary> Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD:
"Gary> Turning PC's into workstations. See http://www.FreeBSD.ORG/
"Gary> for info
"Gary>
I would prefer to get a warning from dump(8), not an error exit.
There may be other cases to consider, in addition to dumping to a
remote system with rdump(8).
E. g. how about dumping to a locally attached device with the
intention of restoring the tape on another system? The other system
may very well be capable of handling blocksizes > 32.
Georg-W. Koltermann, gwk@cray.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606171323.PAA18629>