Tar: Exiting with failure status due to previous errors

Due to git clone is too slow, I now got the pkgsrc.tar.bz2 tarball and extract it.

It’s very slow until tar exited because of errors.

The full log is here: https://pastebin.com/tRD6QRih

Regardless of this, I have a pkgsrc directory on my home dir and going to try a bootstrap.

Your archive contains hard links. Haiku native file system BFS do not support hard links.

1 Like

Any plan to add hard links support?

Yes, in BFS2.

1 Like

When would we have it?

No short or medium term plans.

In haikuports we extract tar archives using Python and convert hardlinks to either symbolic links or file copies.

Or you can use another filesystem for your pkgsrc work, where hardlinks are supported. Maybe ext4 or reiserfs (because I think we have working write support for these two).

1 Like

This information is misleading.

Here is my report about supported file systems on Haiku. Tested on Haiku 64 bit.

NTFS: read/write support

But git clone failed with this:

error: unable to mmap ‘/unnamed volume/pkgsrc/.git/config’: Invalid Argument
fatal: could not set ‘core.filemode’ to ‘false’

Ext4: completely no support at all

Error mounting volume: Bad data

Both read/write or read-only.

Only detected as Ext2.

Ext3: Fastest with git clone, read/write support, only detected as Ext2

Ext2: Slower with git clone, read/write support

ReiserFS: Read-only

Reiser4: Not supported

Here is little investigation on the slowness with git clone.

BeFS: Slowest, git clone stuck at 35%

Ext2, Ext3: git clone could done

Resolving deltas is generally slow.

Extracting tarball is slow.

Stuck after git Updating files done.

The slowness is I/O problem.

It’s not just the own problem of BeFS.

It’s slow for all supported read/write file system.

BTW, I don’t know why my posts are all flagged by the community.

I didn’t spam, nor advertise my product.

My account name, djgpp, is created when I failed to try making djgpp compile and run on Haiku and needs help there.

I’m out of idea, so I just pick the name ‘djgpp’.

I’m just a normal user.

I’m not related with either djgpp or mingw-w64.

Please make it clear about that.

The restriction of your platform for new users caused me to save my posts in notepad before I could post. This is the reason for my abnormally order of posts.

I tested cloning pkgsrc. You can use ‘–depth 10’ to shorten the time.
With tar, you can use the ‘-h’ and/or ‘-O’ options to workaround some of the issues…

~/test-me> time git clone git://wip.pkgsrc.org/pkgsrc-wip.git wip
Cloning into ‘wip’…
remote: Enumerating objects: 434459, done.
remote: Counting objects: 100% (434459/434459), done.
remote: Compressing objects: 100% (185172/185172), done.
remote: Total 434459 (delta 246500), reused 429463 (delta 242593)
Receiving objects: 100% (434459/434459), 365.22 MiB | 400.00 KiB/s, done.
Resolving deltas: 100% (246500/246500), done.
Updating files: 100% (34129/34129), done.

real 19m3.246s
user 2m38.408s
sys 1m15.435s
~/test-me> uname -a
Haiku shredder 1 hrev54154+123 Dec 7 2020 07:52 BePC x86 Haiku

Sorry about that, it wasn’t the community but the forum software. It found you linking several times to the same domain suspicious. Maybe the admin team can loosen these restrictions a bit?
I unflagged your posts, anyway.

1 Like