From owner-freebsd-hackers Thu Jul 26 10:26:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id 6E7EF37B403 for ; Thu, 26 Jul 2001 10:26:30 -0700 (PDT) (envelope-from howardjp@Glue.umd.edu) Received: from z.glue.umd.edu (IDENT:root@z.glue.umd.edu [128.8.10.71]) by po3.glue.umd.edu (8.10.1/8.10.1) with ESMTP id f6QHQSE16553 for ; Thu, 26 Jul 2001 13:26:29 -0400 (EDT) Received: from z.glue.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by z.glue.umd.edu (8.9.3/8.9.3) with SMTP id NAA03732 for ; Thu, 26 Jul 2001 13:26:28 -0400 (EDT) Received: from localhost (howardjp@localhost) by z.glue.umd.edu (8.9.3/8.9.3) with ESMTP id NAA03728 for ; Thu, 26 Jul 2001 13:26:28 -0400 (EDT) X-Authentication-Warning: z.glue.umd.edu: howardjp owned process doing -bs Date: Thu, 26 Jul 2001 13:26:28 -0400 (EDT) From: James Howard To: freebsd-hackers@freebsd.org Subject: Backup file formats: tar, cpio, pax, yadda, yadda, yadda Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Both tar and cpio seem to have problems doing backups on my server. Looking at the pax manpage, we see this: cpio The extended cpio interchange format specified in the IEEE Std 1003.2 (``POSIX.2'') standard. The default blocksize for this format is 5120 bytes. Inode and device informa- tion about a file (used for detecting file hard links by this format) which may be truncated by this format is detected by pax and is repaired. bcpio The old binary cpio format. The default blocksize for this format is 5120 bytes. This format is not very portable and should not be used when other formats are available. Inode and device information about a file (used for detecting file hard links by this format) which may be truncated by this format is detected by pax and is repaired. sv4cpio The System V release 4 cpio. The default blocksize for this format is 5120 bytes. Inode and device information about a file (used for detecting file hard links by this format) which may be truncated by this format is detected by pax and is repaired. sv4crc The System V release 4 cpio with file crc checksums. The default blocksize for this format is 5120 bytes. Inode and device information about a file (used for detecting file hard links by this format) which may be truncated by this format is detected by pax and is repaired. tar The old BSD tar format as found in BSD4.3. The default blocksize for this format is 10240 bytes. Pathnames stored by this format must be 100 characters or less in length. Only regular files, hard links, soft links, and directories will be archived (other file system types are not supported). For backwards compatibility with even older tar formats, a -o option can be used when writing an archive to omit the storage of directories. This option takes the form: -o write_opt=nodir ustar The extended tar interchange format specified in the IEEE Std 1003.2 (``POSIX.2'') standard. The default blocksize for this format is 10240 bytes. Pathnames stored by this format must be 250 characters or less in length. Let's review. All the tar formats will truncate long filenames. All the cpio formats truncate the inode number. Is there a reasonable backup tool which does not do goofy things like that? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message