From: Eric Sandeen <sandeen@redhat.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: mkfs+mount failure of small fs on ppc64
Date: Thu, 15 Sep 2016 09:07:30 -0500 [thread overview]
Message-ID: <e5b1dbda-c244-a550-0a58-443b17408d59@redhat.com> (raw)
In-Reply-To: <2210b649-c379-106a-2de4-923a0ce55593@redhat.com>
On 9/13/16 4:44 PM, Eric Sandeen wrote:
> on ppc64, 4.7-rc kernel, git btrfs-progs, v4.7.2:
>
> # truncate --size=500m testfile
> # ./mkfs.btrfs testfile
> # mkdir -p mnt
> # mount -o loop testfile mnt
Same failure on aarch64 if that makes it any more interesting. ;)
# mount -o loop testfile mnt
mount: mount /dev/loop0 on /root/mnt failed: No space left on device
Sector size issue I guess, driven by page size.
-Eric
> btrfs-progs v4.7.2
> See http://btrfs.wiki.kernel.org for more information.
>
> Label: (null)
> UUID: c531b759-a491-4c9f-a954-4787cea9106d
> Node size: 65536
> Sector size: 65536
> Filesystem size: 500.00MiB
> Block group profiles:
> Data: single 8.00MiB
> Metadata: DUP 32.00MiB
> System: DUP 8.00MiB
> SSD detected: no
> Incompat features: extref, skinny-metadata
> Number of devices: 1
> Devices:
> ID SIZE PATH
> 1 500.00MiB testfile
>
>
> # dmesg -c
> [ 61.210287] loop: module loaded
> [ 61.247105] BTRFS: device fsid a8d79cd0-977f-4b93-8410-246dc08b3683 devid 1 transid 5 /dev/loop0
> [ 61.247391] BTRFS info (device loop0): disk space caching is enabled
> [ 61.247397] BTRFS info (device loop0): has skinny extents
> [ 61.270492] BTRFS info (device loop0): creating UUID tree
> [ 61.312149] BTRFS warning (device loop0): failed to create the UUID tree: -28
> [ 61.483028] BTRFS: open_ctree failed
>
> 2nd mount works:
>
> # mount -o loop testfile mnt
> # dmesg -c
> [ 87.504564] BTRFS info (device loop0): disk space caching is enabled
> [ 87.504579] BTRFS info (device loop0): has skinny extents
> [ 87.506979] BTRFS info (device loop0): creating UUID tree
>
> Any ideas? This seems to have regressed since 3.9.1, but there are a couple
> other mkfs breakages in between, and my bisect was not fruitful.
>
> Thanks,
> -Eric
> --
> 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
>
prev parent reply other threads:[~2016-09-15 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 21:44 mkfs+mount failure of small fs on ppc64 Eric Sandeen
2016-09-15 14:07 ` Eric Sandeen [this message]
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=e5b1dbda-c244-a550-0a58-443b17408d59@redhat.com \
--to=sandeen@redhat.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).