From owner-freebsd-questions Tue Jun 5 6:45:23 2001 Delivered-To: freebsd-questions@freebsd.org Received: from hercules.crossthread.com (hercules.crossthread.com [139.142.137.241]) by hub.freebsd.org (Postfix) with ESMTP id 3D6DE37B403 for ; Tue, 5 Jun 2001 06:45:20 -0700 (PDT) (envelope-from timp@crossthread.com) Received: from dedalus (IRCUser@h24-67-125-159.cg.shawcable.net [24.67.125.159]) (authenticated) by hercules.crossthread.com (8.11.3/8.11.3) with ESMTP id f55DoWw86075 for ; Tue, 5 Jun 2001 07:50:32 -0600 (MDT) From: "Tim Pushor" To: Subject: cpio weirdness Date: Tue, 5 Jun 2001 08:13:37 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal 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 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