Downloaded stage3 from OSU and tried to untar to my JFS root drive. I noticed an error go by in the filenames...so I tried to redirect stdout to a file. Then I got the below text (after running "tar -xvjpf stage3-*.tar.bz2>tarout"... jfs_strtoUCS: char2uni returned -22 charset = iso8859-1, char = 0x99 tar: ./usr/share/doc/kbd-1.08-r4/html/utf/\342\231\252\342\231\254: Cannot open: Invalid argument tar: Error exit delayed from previous errors Reproducible: Didn't try Steps to Reproduce: 1. Boot with 20040128 Live CD 2. Created ext3 boot, a swap, and a jfs root partition 3. mounted root and boot (after creating boot dir on root) 4. used links to download stage3 tarball from OSU's experimental x86 dir to /mnt/gentoo 5. ran "tar -xvjpf stage3-*.tar.bz2>tarout" without quotes Actual Results: Got error listed in description Expected Results: No errors (and correct files in correct places, etc)
Also happens with downloaded v1.08-r5 package (when tried to "emerge system"). Downloaded from "http://gentoo.oregonstate.edu/distfiles/kbd-1.08.tar.gz". This time the error text is... "... >>> Unpacking source... >>> Unpacking kbd-1.08.tar.gz to /var/tmp/portage/kbd-1.08-r5/work jfs_strtoUCS: iso8859-1, char = 0x99 tar: ./kbd-1.08/doc/utf/\342\231\252\342\231\254: Cannot open: Invalid argument tar: Error exit delayed from previous errors !!! ERROR: sys-apps/kbd-1.08-r5 failed. !!! Function unpack, Line 306, Exitcode 2 !!! failure unpacking kbd-1.08.tar.gz"
Still happens with stage1-x86-20040204.tar.bz2 when attempt to run "emerge system" after bootstrap.sh completed.
See this one on LKML http://lkml.org/lkml/2004/2/11/105 Will try to set a default NLS next time
I'm getting the same problem as comment #1 with kbd errors on JFS... is there a temporary work-around for this?
beejay, was this taken care of?
I am still getting same error message as Comment #1. I am very new to Linux (and Gentoo) and was following the gentoo installation handbook from stage 1. It had said that using any filesystem would work, although this appears to be a file system bug (jfs). It would be nice if we could fix this bug or update the gentoo installation handbook (http://www.gentoo.org/doc/en/handbook/handbook.xml?part=1&chap=4#doc_chap9) so as to not recommend using the JFS for the / mount point.
Is this *ever* going to be fixed??? Can we get SOME kind of work around, or something? I'm using JFS for a reason.
KBD also fails on stage-2 installs when using the JFS FS with both universal and minimal live CDs and with a variety of errors. see these forum post for more details: http://forums.gentoo.org/viewtopic.php?t=153261 http://forums.gentoo.org/viewtopic.php?t=135070 http://forums.gentoo.org/viewtopic.php?t=157494
So this is still an issue with 2004.1?
let me try and dig up some extra hardware to test this on ...
Is this even an issue if you use the CD in http://dev.gentoo.org/~wolf31o2/releng to boot from? Since those JFS fixes were made a while back (February), I would think they had made it into our kernel tree. Not to mention, we have a default NLS set.
Still happens when unpacking as initially described (I assume it will in the second case I listed below too). I just tested with 2004.1 minimal CD and the current x86 stage3 tar.
I really need you to test with *my* CD, otherwise this will not get fixed for 2004.2, as my CDs are the proving grounds for new technologies for 2004.2. Thanks
With gentoo-2004.2-test4.iso and newest experimental stage3.bz2 I got only the bottom two lines of the previous error. tar: ./usr/share/doc/kbd-1.08-r5/html/utf/\342\231\252\342\231\254: Cannot open: Invalid argument tar: Error exit delayed from previous errors So I guess those were two seperate errors. Should I open another bug for this one?
There is no need to open another bug, as it appears that the issue is simply with the JFS version on the CD. I am going to assume that you are using the "gentoo" kernel and not the "smp" kernel, correct? Could you try again with the "smp" kernel on that CD?
Joe, what if you mount your JFS with "-t jfs -o iocharset=utf8"? Also, you need to set CONFIG_NLS_DEFAULT in your kernel.
I have find this problem also installing from this iso: install-x86-universal-2004.2.iso when I untar the stage3 in a raiserFS on the shell are printed this error: tar: Error exit delayed from previous errors i have check the MD5sum of the iso, and is correct. This mean that the stage3*.tar.bz on this live cd are bud I think. i have tryed with both stage3*x86*.tar.bz and stage3*i686*.tar.bz . here the (is correct, i've already check) md5: df2dd58ea0afc7a1d7b94a518097f809
Are you POSITIVE that the tar error is really an error and not a result of being unable to create a .keep file in /proc (which you probably have bind mounted)?
It appears that this still persists even on the latest LiveCD... is this something you guys can fix or know of a workaround that we can employ that works?
Related to #58428 ?
They look to be similar, and could even be the same problem, but since I don't use JFS, I am not very familiar with it to tell you authoratatively.
Can you try one of the new -test series at /experimental/x86/livecd/x86 on your favorite mirror? I am hoping this has been fixed in later kernels.
I honestly can't tell you when or what fixed this, but I just tested this with 2005.0, and it works flawlessly.
