From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: mkfs.btrfs - error checking /dev/sda5 mount status
Date: Tue, 8 Feb 2011 21:26:49 +0000 (UTC) [thread overview]
Message-ID: <iiscep$udg$1@dough.gmane.org> (raw)
In-Reply-To: 4D51A0D9.9000701@libero.it
Goffredo Baroncelli, Tue, 08 Feb 2011 21:00:25 +0100:
> On 02/08/2011 07:57 AM, Lubos Kolouch wrote:
>> Hi,
>>
>> I'm hitting this issue - sda5 is a normal device, nothing to do with
>> loop, encryption etc.
>>
>> # mkfs.btrfs /dev/sda5
>>
>> WARNING! - Btrfs v0.19-35-g1b444cd-dirty IS EXPERIMENTAL WARNING! - see
>> http://btrfs.wiki.kernel.org before using
>>
>> error checking /dev/sda5 mount status
>>
>> Is there something I can do to resolve this?
>
> Some months ago I posted a patch [*] which allows to create a filesystem
> even if an integrity tests fail.
> Anyway it would be interesting understand why mkfs.btrfs fails. It is
> possible to have a strace of the command ?
>
here ... http://paste.pocoo.org/show/334638/
but it is not in chroot, it is in "normal" system
Lubos
next prev parent reply other threads:[~2011-02-08 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 6:57 mkfs.btrfs - error checking /dev/sda5 mount status Lubos Kolouch
2011-02-08 20:00 ` Goffredo Baroncelli
2011-02-08 21:26 ` Lubos Kolouch [this message]
2011-02-09 18:25 ` Goffredo Baroncelli
2011-02-09 20:12 ` Lubos Kolouch
2011-02-10 3:09 ` Chris Samuel
2011-02-10 6:54 ` Lubos Kolouch
2011-02-10 7:49 ` Helmut Hullen
2011-02-10 7:47 ` Helmut Hullen
2011-02-10 18:24 ` Goffredo Baroncelli
2011-02-10 18:35 ` Lubos Kolouch
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='iiscep$udg$1@dough.gmane.org' \
--to=lubos.kolouch@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.