From owner-freebsd-questions Mon Jun 21 9:35:58 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id 13BC714FB5 for ; Mon, 21 Jun 1999 09:35:50 -0700 (PDT) (envelope-from doranj@ucsu.Colorado.EDU) Received: (from doranj@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) id KAA06413 for freebsd-questions@freebsd.org; Mon, 21 Jun 1999 10:35:49 -0600 (MDT) From: Jonathon Doran Message-Id: <199906211635.KAA06413@ucsu.Colorado.EDU> Subject: Re: Bug in tar/FreeBSD To: freebsd-questions@freebsd.org Date: Mon, 21 Jun 1999 10:35:49 -0600 (MDT) In-Reply-To: <376E6284.CA15EA05@stcinc.com> from "Gregory Carvalho" at Jun 21, 99 09:04:20 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On FreeBSD 3.1-Release (Walnut Creek CDROM), tar -cv reports it has > archived all data. Executing tar -tv outputs a listing which stops at > etype in /proc. I have two systems running 3.1. One has a DDS2 (via > AHA-2940UW) the other a DDS3 (via AHA-2940U2W). Using tar -tv, the DDS2 > stops at /proc/3434/etype (several entry lines above this is > /proc/curproc -> 3432), and the DDS3 stops at /proc/261/etype > (/proc/curproc has no link). Below this point tar -cv outputed more > files and dirs including /dist, /bin, /boot, /lkm, /mnt, /modules, > /root, /sbin, and root files. I've reproduced this error on 3.2RELEASE. There appears to be a problem when writing some files in /proc to an archive, although tar did report errors for me. (Greg: are you using a cron job here?) Output from tar: doransw# tar cvf /home/tmp/test2.tar ./proc ./proc/ ./proc/curproc ./proc/26640/ ./proc/26640/file ./proc/26640/mem ./proc/26640/regs ./proc/26640/fpregs ./proc/26640/ctl ./proc/26640/status ./proc/26640/note ./proc/26640/notepg ./proc/26640/map tar: read error at byte 0, reading 76 bytes, in file ./proc/26640/map : File too large ./proc/26640/etype tar: file ./proc/26640/etype shrunk by 64 bytes, padding with zeros. ./proc/26640/cmdline A suitable workaround might be to use the "-l" or "-one-file-system" flag to tar to keep it out of /proc. Another would be to create a file list with "cd /; find . -prune /proc -prune /tmp > /tmp/tape.list" and then write the tape like "tar -cvf /dev/rsa0 -C / -T /tmp/tape.list > /tmp/tape.out" Looks like something fun to look into! (I think it would be nice to have a -prune in tar for cases like this, BTW). Jon Doran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message