From: Roman Mamedov <rm@romanrm.ru>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: mkfs.btrfs fails on ARM
Date: Fri, 17 Feb 2012 00:51:26 +0600 [thread overview]
Message-ID: <20120217005126.7beebd82@natsu> (raw)
In-Reply-To: <20120216220811.534cbf02@natsu>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Thu, 16 Feb 2012 22:08:11 +0600
Roman Mamedov <rm@romanrm.ru> wrote:
> # mkfs.btrfs /dev/loop7
>
> WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
> WARNING! - see http://btrfs.wiki.kernel.org before using
>
> mkfs.btrfs: volumes.c:1575: btrfs_read_chunk_tree: Assertion `!(ret)' failed.
> Aborted
I reran the command on a 1GB loop device (with the same result), and here is
its gzipped image: http://media.romanrm.ru/tmp/btrfs-made-on-arm.img.gz (1MB)
This can't be opened by btrfsck with the same error message, and on amd64 too.
btrfsck: volumes.c:1575: btrfs_read_chunk_tree: Assertion `!(ret)' failed.
So the problem is clearly with mkfs on ARM, creating an invalid FS.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-02-16 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 16:08 mkfs.btrfs fails on ARM Roman Mamedov
2012-02-16 18:51 ` Roman Mamedov [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=20120217005126.7beebd82@natsu \
--to=rm@romanrm.ru \
--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).