From owner-freebsd-questions Tue Jun 5 6:52:27 2001 Delivered-To: freebsd-questions@freebsd.org Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (Postfix) with ESMTP id 65D4337B401 for ; Tue, 5 Jun 2001 06:52:23 -0700 (PDT) (envelope-from shovey@buffnet.net) Received: from buffnet11.buffnet.net (buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.9.3/8.8.7) with ESMTP id JAA21036; Tue, 5 Jun 2001 09:54:23 -0400 (EDT) (envelope-from shovey@buffnet.net) Date: Tue, 5 Jun 2001 09:52:05 -0400 (EDT) From: Stephen Hovey To: Tim Pushor Cc: questions@FreeBSD.ORG Subject: Re: cpio weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cpio has bugs - I switched to pax for that exact reason On Tue, 5 Jun 2001, Tim Pushor wrote: > Hello, > > I recently backed up a system using cpio so I could re-layout the > filesystems, and then restore into the new filesystm setup. > > This is something I have done several times before. > > This time though, things went weird. Upon restore, many files were not > properly restored (it is probably more accurate to say they were not backed > up properly). > > The main symptom I see is that a bunch of files got created as (or linked > to) device nodes. This is a portion of a directory listing of /usr/bin: > > -r-xr-xr-x 1 root wheel 5996 Jun 4 17:01 xargs > -r-xr-xr-x 1 root wheel 7688 Jun 4 17:01 xstr > crw-r----- 4 root operator 43, 0x00030002 Jun 4 17:01 yacc > -r-xr-xr-x 1 root wheel 3120 Jun 4 17:01 yes > -r-xr-xr-x 1 root wheel 4472 Jun 4 17:01 ypcat > crw-r----- 8 root operator 13, 0x0004001a Jun 4 17:01 ypchfn > crw-r----- 8 root operator 13, 0x0004001a Jun 4 17:01 ypchpass > crw-r----- 8 root operator 13, 0x0004001a Jun 4 17:01 ypchsh > -r-xr-xr-x 1 root wheel 4536 Jun 4 17:01 ypmatch > crw-r----- 4 root operator 3, 0x00010002 Jun 4 17:01 yppasswd > -r-xr-xr-x 1 root wheel 6384 Jun 4 17:01 ypwhich > -r-xr-xr-x 1 root wheel 2475 Jun 4 17:01 yyfix > crw-r----- 6 root operator 9, 6 Jun 4 17:01 zcat > crw-r----- 4 root operator 9, 5 Jun 4 17:01 zcmp > crw-r----- 4 root operator 9, 5 Jun 4 17:01 zdiff > -r-xr-xr-x 6 root wheel 52132 Jun 4 17:01 zegrep > -r-xr-xr-x 6 root wheel 52132 Jun 4 17:01 zfgrep > -r-xr-xr-x 1 root wheel 919 Jun 4 17:01 zforce > -r-xr-xr-x 6 root wheel 52132 Jun 4 17:01 zgrep > -r-xr-xr-x 1 root wheel 1112 Jun 4 17:01 zmore > -r-xr-xr-x 1 root wheel 3545 Jun 4 17:01 znew > > The cpio listing (cpio -ivt) for the errant files looks weird as well (note > 0 bytes, but only 2 links): > > -r-xr-xr-x 2 root wheel 0 Apr 21 03:09 usr/bin/yacc > > > The reason I am concerned is this is usually how I backup and restore > systems. > > The OS in question is FreeBSD 4.3-RELEASE > The CPIO command was quite simple. I first prepared a file list of files to > backup, then performed: > > cat filelist | cpio -oH crc > backup.cpio > > I restored the archive using > > cpio -ivd < backup.cpio > > Thanks for any and all comments. > Tim > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message