From: Saul Wold <sgw@linux.intel.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Issue building a file based rootfs image with mkfs.btrfs
Date: Sun, 22 Sep 2013 11:28:01 -0700 [thread overview]
Message-ID: <523F36B1.8080701@linux.intel.com> (raw)
In-Reply-To: <523B4036.7030204@linux.intel.com>
On 09/19/2013 11:19 AM, Saul Wold wrote:
>
> Hi there,
>
> I am attempting to build a rootfs image from an existing rootfs
> directory tree. I am using the 0.20 @ 194aa4a of Chris's git repo.
>
> The couple problem I saw was that the target image file needed to exist,
> although I think I can patch that then the FS size was much larger than
> the actual size, I tracked this to the usage of ftw not accounting for
> symlinks, I have a patch for that which I will send once I finish
> getting the other issues resolved.
>
> Next issue I hit was an assertion failure after getting "not enough free
> space" message:
>
> not enough free space
> add_file_items failed
> unable to traverse_directory
> Making image is aborted.
> mkfs.btrfs: mkfs.c:1542: main: Assertion `!(ret)' failed.
>
> I am kind of stuck on this one, took it as far as I can right now. Would
> I be better off dropping back to 0.19 or can we move forward fixing this?
>
Anybody have any ideas on this? I can reproduce this at will on Fedora
19 (with btrfs-progs-0.20), Ubuntu 12.10 (with btrfs-profs-0.19) and
with HEAD from Chris's repo above (is this the right place these days)?
Thanks your your help.
Sau!
> Thanks
>
next prev parent reply other threads:[~2013-09-22 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 18:19 Issue building a file based rootfs image with mkfs.btrfs Saul Wold
2013-09-22 18:28 ` Saul Wold [this message]
2013-09-28 12:29 ` Chris Mason
2013-09-28 17:51 ` Saul Wold
2013-10-01 14:35 ` David Sterba
2013-10-01 14:56 ` Wang Shilong
2013-10-01 20:50 ` Saul Wold
2013-10-02 1:18 ` Chris Mason
2013-10-14 15:25 ` Saul Wold
2013-10-14 15:26 ` Chris Mason
2013-10-14 20:51 ` Chris Mason
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=523F36B1.8080701@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).