From owner-freebsd-questions Fri Jan 8 20:30:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10560 for freebsd-questions-outgoing; Fri, 8 Jan 1999 20:30:17 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10555 for ; Fri, 8 Jan 1999 20:30:12 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (Tambler.infowest.com [207.49.57.143]) by infowest.com (8.8.8/8.8.8) with ESMTP id VAA06369 for ; Fri, 8 Jan 1999 21:29:58 -0700 (MST) Message-ID: <3696DB34.29D87B41@infowest.com> Date: Fri, 08 Jan 1999 21:29:40 -0700 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: questions@FreeBSD.ORG Subject: Re: Why won\'t TAR cooperate\? References: <199901070249.TAA02192@infowest.com> <19990107190309.446.qmail@alice.gba.oz.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Black wrote: <> > Try it with dd to ensure that you can read the file and write > the whole thing to the tape: > > dd if=big_file obs=64k of=/dev/tape_device > > -- > Greg Black Thanks, dd in fact worked perfectly. I even used tar and piped the output of tar to dd and that worked: # tar --create --file - really_big_file | dd of=/dev/nrst0 obs=65536 65575+1 records in 65575+1 records out 4297551657 bytes transferred in 982.901416 secs (4372312 bytes/sec) # mt -f /dev/nrst0 weof # mt -f /dev/nrst0 rewind # dd if=/dev/nrst0 obs=65536 of=really_big_file2 65575+1 records in 65575+1 records out 4297551657 bytes transferred in 1319.829718 secs (3256141 bytes/sec) # diff --brief --report-identical-files really_big_file and really_big_file Files really_big_file and really_big_file2 are identical It still puzzles me that tar when used alone always stopped at the same spot every time I tried it. I've used tar just fine on other huge files saved to HD instead of tape, but try as I might, tar would not write the large file to my tape. The only supposition I can fathom at this point is that tar believed that the tape was shorter than it really was. Oh, I did forget to mention in my second post that I'm running 2.2.8-RELEASE/STABLE (RELEASE user land and STABLE kernel). Kevin Street wrote: >Do the login.conf filesize settings apply to tapes? What does `limits' >say yours is set to? Hmmm, once I 'su' to root (which I did) would this matter? Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message