From: Saul Wold <sgw@linux.intel.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Issue building a file based rootfs image with mkfs.btrfs
Date: Sat, 28 Sep 2013 10:51:54 -0700 [thread overview]
Message-ID: <5247173A.1090301@linux.intel.com> (raw)
In-Reply-To: <20130928122952.31924.54312@localhost.localdomain>
On 09/28/2013 05:29 AM, Chris Mason wrote:
> Quoting Saul Wold (2013-09-19 14:19:34)
>> 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?
>
> Hi Saul,
>
> Update on my end, the problem is the image code expects every file to
> fit inside a single chunk. It's only creating 8MB chunks, so any file
> over 8MB in size is causing problems.
>
> I'm fixing it up here, I should have a patch for you on Monday.
>
Ah great news! I want to verify is your git repo for btrfs-progs the
main upstream? I see loads of other patches flying around, but not
applied there.
Thanks again
Sau!
> Thanks!
>
> -chris
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-09-28 17:51 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
2013-09-28 12:29 ` Chris Mason
2013-09-28 17:51 ` Saul Wold [this message]
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=5247173A.1090301@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=chris.mason@fusionio.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).