[SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

Vi0L0 · 2012-01-07 14:13:45

I'm not sure is this best place to post this problem, but guess yes, so...

I'm having troubles with kernel's compilation (i'm using AUR's linux-mainline package as a base). Firstly i thought that problem lays in my config which differs in many places from the default one, but then i tried to compile linux-mainline "as is", still with same error.
Here's the problem: after succesfull compilation and while package compression i'm getting this:

bsdtar: usr/src/linux-3.2.0-1-mainline/vmlinux: Truncated write; file may have grown while being archived.

I actually didn't even try is kernel built with such error working, after it's installation i just saw that external modules cannot be compiled on it and so i just downgraded to 3.2rc7 which i built some time ago.
Then i though - what about building 3.2rc7 again - will it pass now?
Checked, and no - still same bsdtar's error.

I actually don't know where's the problem - i somehow feel that it has to do something with libarchive package - one of those which were updated lately.
I built 3.2 rc7 kernel succesfully when it was released (on christmass i guess) on old libarchive 2.8.5-2, now i can not, so yeah i guess it's libarchive fault.

Any idea how to solve this?

BTW my makepkg.conf file differs only a little of default makepkg.conf file:
CFLAGS="-mtune=core2 -march=core2 -m64 -mssse3 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="-mtune=core2 -march=core2 -m64 -mssse3 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
+ sign

Last edited by Vi0L0 (2012-01-09 22:39:49)

falconindy · 2012-01-07 15:13:27

makepkg.conf flags aren't used by Kbuild. I've noticed this too when building my own kernel package. Its harmless except for messing up the vmlinux ELF (meaning external module compilation isn't possible) . Haven't had time to figure where my own pkg is wrong. The official PKGBUILD is fine.

det · 2012-01-08 14:29:50

I get this even with the official/default PKGBUILD/config/makepkg.conf.

E: Actually, Vi0L0 was right. This is indeed caused by libarchive 3.x from [testing].

Last edited by det (2012-01-08 14:57:34)

falconindy · 2012-01-08 15:57:36

Interesting... I can only reproduce it on an actual disk -- building in tmpfs is fine.

det · 2012-01-08 16:19:30

Lol. At first I just thought you messed something up but that's actually true.

Probably related to this atime thing: http://projects.archlinux.org/svntogit/ … 4b33768730

[...]
+  # currently fails in a minor test involving atime updates (#60)
+  make check || :

So the problem's just some timing issue when the archive is being written to disk. When it's done in just RAM everything works fine.

falconindy · 2012-01-08 17:44:30

Completely unrelated.

http://code.google.com/p/libarchive/iss … ail?id=222

Last edited by falconindy (2012-01-08 18:00:47)

det · 2012-01-09 14:08:24

Wow, already fixed (just tried the patch myself) .

Thanks for your contribution, falconindy!

Vi0L0 · 2012-01-09 22:39:12

Big thanks to falconindy and kientzle.
Patch works great.

Guess it will soon be fixed in upcoming libarchive's release, solved.

b_m_l · 2012-01-14 20:05:16

its not working for me. maybe im doing it wrong? i download the 3.0.3 version of libarchive, but when i ./configure make make install i still have the 2.8.5-2 version. i want to install nvidia drivers and its killed with the vmlinux is truncated error. any ideas? also tried to update the whole system (maybe new kernel?) i have arch linux 3.1.9-1 kernel

karol · 2012-01-14 20:08:53

b_m_l, you should be using PKGBUILDs and not ./configure make make install i by hand as pacman won't see apps that you installed that way.
If you did build libarchive with makepkg, make sure you installed the new package.

b_m_l · 2012-01-14 20:18:40

karol wrote:

b_m_l, you should be using PKGBUILDs and not ./configure make make install i by hand as pacman won't see apps that you installed that way.
If you did build libarchive with makepkg, make sure you installed the new package.

yes i tried that but there were errors too, it was trying to acces a 3.2 kernel directory (but it did not exist) now i added the testing repository, found there the 3.0.3 libarchive, when i wanted to install that he errors libarchive.so.2 cannot open shared object file. and now i cant do anything. no cmake no pacman no yaourt. do i have to reinstall the whole system? confusing.....sorry but im pretty new to arch

Arch Linux

#1 2012-01-07 14:13:45

[SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#2 2012-01-07 15:13:27

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#3 2012-01-08 14:29:50

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#4 2012-01-08 15:57:36

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#5 2012-01-08 16:19:30

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#6 2012-01-08 17:44:30

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#7 2012-01-09 14:08:24

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#8 2012-01-09 22:39:12

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#9 2012-01-14 20:05:16

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#10 2012-01-14 20:08:53

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

#11 2012-01-14 20:18:40

Re: [SLVD] problem with kernel's build: "bsdtar: vmlinux: Truncated write"

Board footer