Date: Tue, 19 Aug 2008 23:30:18 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Dimitry Andric <dimitry@andric.com> Cc: Garrett Cooper <yanefbsd@gmail.com>, current@freebsd.org Subject: Re: Possible regression with 200807 amd64 snapshot CD Message-ID: <48ABB9FA.7050604@freebsd.org> In-Reply-To: <48A9D8D5.7050504@andric.com> References: <7d6fde3d0808172305h219231e2sad939eacb685414e@mail.gmail.com> <48A9D8D5.7050504@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: >>When trying to install 7.0-RELEASE on amd64 with the snapshot CD for >>8.0-CURRENT, I'm running into issues where I can't seem to install >>because the installer gets to a point where it just quits with a -1 >>exit code. >> >>Looking at the console I see a load of "cpio: malformed number" >>messages scroll by the screen, which makes me think that the issue >>lays with either the integrity of the archives received, or there's a >>bug with cpio that's included in the snapshot CD. Dimitry Andric followed up with: > It's the same with 8.0-CURRENT-200807-i386-disc1.iso. Even GNU cpio > doesn't eat the files (for example base.??): > > cpio: Malformed number 000755 > cpio: Malformed number 000000 > [...] > > file(1) says the uncompressed data looks like a POSIX tar archive, and > GNU tar can uncompress it alright: > > drwxr-xr-x root/wheel 0 2008-07-16 00:08 ./ > drwxr-xr-x root/wheel 0 2008-07-16 00:07 ./bin/ > [...] What version? What does "tar --version" show? > While GNU cpio shows something completely different: > > dr-sr-s--T 1 0 root 0 Feb 7 2006 ./ > dr-sr-s--T 1 0 root 0 Feb 7 2006 ./bin/ > dr-sr-s--T 1 0 root 0 Feb 7 2006 ./boot/ > [...] What version? What does "cpio --version" show? I haven't tried to reproduce Garrett's problem yet, but I did just download the 8.0-CURRENT-200807-i386-disc1.iso file that Dimitry reported problems with and extracted the base.?? files from it. I get the right output with any of the following: * bsdcpio 1.0 * bsdtar 2.5.5 * GNU tar 1.19 * GNU cpio 2.6 * FreeBSD pax So far, I've only managed to reproduce the screwed-up output with GNU cpio 2.9. I'm going to dig a little deeper to see if this is really a bug in GNU cpio 2.9 or if there's some error in the data that all those other programs are overlooking. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48ABB9FA.7050604>