From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10141] Squashfs extended attribute failures
Date: Fri, 02 Feb 2018 21:39:25 +0000 [thread overview]
Message-ID: <bug-10141-163-lVQiburr5z@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10141-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10141
Bob <cmg427@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #9 from Bob <cmg427@hotmail.com> ---
This issue still affects me. I'm using fakeroot and mksquashfs to build
multiple squashfs from different mounts.
Some context... I'm building 5 fairly large squashfs in parallel.
The xattrs intermittently fail to get copied over. The more xattrs I have and
the more squashfs I'm building in parallel, the more it will fail to copy over
the xattrs.
Each squashfs is about 500mb in size.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-02-02 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:01 [Buildroot] [Bug 10141] New: Squashfs extended attribute failures bugzilla at busybox.net
2017-08-02 15:06 ` [Buildroot] [Bug 10141] " bugzilla at busybox.net
2017-08-02 20:56 ` bugzilla at busybox.net
2017-08-02 21:26 ` bugzilla at busybox.net
2017-08-03 13:54 ` bugzilla at busybox.net
2017-08-08 20:33 ` bugzilla at busybox.net
2017-08-13 21:35 ` bugzilla at busybox.net
2017-08-13 21:50 ` bugzilla at busybox.net
2017-08-15 16:19 ` bugzilla at busybox.net
2018-02-02 21:39 ` bugzilla at busybox.net [this message]
2018-02-03 13:56 ` bugzilla at busybox.net
2018-02-05 17:35 ` bugzilla at busybox.net
2018-02-05 18:10 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-10141-163-lVQiburr5z@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.