public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Building a brtfs filesystem < 70M?
Date: Tue, 11 Mar 2014 10:38:11 +0800	[thread overview]
Message-ID: <1394505491.6207.4.camel@localhost.localdomain> (raw)
In-Reply-To: <531E4A02.5010404@linux.intel.com>

On Mon, 2014-03-10 at 16:25 -0700, Saul Wold wrote:
> Hi There
> 
> There seems to be an issue if we try to build a btrfs based FS that is 
> less than 70M, we get the following assertion failure:
> 
> mkfs.btrfs: extent-tree.c:2682: btrfs_reserve_extent: Assertion `!(ret)' 
> failed.
> 
> I tried to do a search on this and did not find anything obvious.
> 
> Further, if I do build a 70M image, it will not mount until I get to I 
> increase  the about 100M!
> 
> # mount -o loop -v rootfs.btrfs mnt
> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
>         missing codepage or helper program, or other error
> 
>         In some cases useful info is found in syslog - try
>         dmesg | tail or so.
> 
> I can provide a small rootfs (~4M) example if needed
> 
> Builds and mounts correct:
> mkfs.btrfs -b 104857600 -r rootfs rootfs.btrfs
> 
> Builds, but does not mount:
> mkfs.btrfs -b 73400320 -r rootfs rootfs.btrfs
> 
> Does not build, gives the above assertion error:
> mkfs.btrfs -b 10889216 -r rootfs rootfs.btrfs
> 
> 
> Thanks
> 
Hi Saul,
Sorry, I'm not able to reproduce your problem...
Are you running the latest btrfs-progs from david's branch?

Thanks,
Gui



  parent reply	other threads:[~2014-03-11  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 23:25 Building a brtfs filesystem < 70M? Saul Wold
2014-03-11  0:16 ` cwillu
2014-03-11  2:38 ` Gui Hecheng [this message]
2014-03-11  3:16   ` Saul Wold
2014-03-11  5:47     ` Gui Hecheng
2014-03-11  6:41       ` Saul Wold
2014-03-11  7:51         ` Gui Hecheng
2014-03-11 16:37 ` Zach Brown
2014-03-12  1:10   ` quwenruo
2014-03-12  1:43     ` Saul Wold

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=1394505491.6207.4.camel@localhost.localdomain \
    --to=guihc.fnst@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sgw@linux.intel.com \
    /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