All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>, Anand.Jain@oracle.com
Subject: Re: mkfs.btrfs broken
Date: Thu, 07 Mar 2013 09:13:26 -0600	[thread overview]
Message-ID: <5138AE96.3020304@redhat.com> (raw)
In-Reply-To: <5138ADA6.5070101@petaramesh.org>

On 3/7/13 9:09 AM, Swâmi Petaramesh wrote:
> Le 07/03/2013 14:37, Eric Sandeen a écrit :
>> What error messages does it emit, anything helpful? 
> 
> root@partedmagic:~# file -s /dev/sda5
> /dev/sda5: data
> 
> root@partedmagic:~# mkfs.btrfs /dev/sda5
> 
> WARNING! - Btrfs v0.20-rc1 IS EXPERIMENTAL
> WARNING! - see http://btrfs.wiki.kernel.org before using
> 
> error checking /dev/sda5 mount status

Ok, so that's unhelpful isn't it.  :)

> root@partedmagic:~# echo $?
> 1
> 
>> The option is quite new, and still exists upstream. But it only forces
>> overwrite of an existing filesystem, it has never affected the mount
>> status check AFAIK. 
> 
> I remember that, in the past, I was several time able to override this
> very error by using a -f switch...
> 

maybe it was some non-upstream hack I'm not aware of.

>> There are also steps you could take to investigate some more yourself:
>> Did earlier versions of the livecd work for you? If so, when did it break?
> 
> It was broke first time I tried to use it more than a year ago ; I don't
> clearly remember if it has been fixed at some point in time... I'm
> positively sure that I saw the exact same error on other live distros
> (possibly Ubuntu but not sure...)
> 
>> Can you capture an strace of the failing mkfs.btrfs? -Eric 
> I don't know how to do this, I'm no developper myself...

# strace -o tracefile.txt mkfs.btrfs /dev/sda5

tracefile.txt will contain all syscalls made by the binary and their results,
which might give us a clue what's gone wrong.

-Eric

> Kind regards.
> 


  reply	other threads:[~2013-03-07 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 12:11 mkfs.btrfs broken Swâmi Petaramesh
2013-03-07 13:37 ` Eric Sandeen
2013-03-07 15:09   ` Swâmi Petaramesh
2013-03-07 15:13     ` Eric Sandeen [this message]
2013-03-07 15:21       ` Swâmi Petaramesh
2013-03-07 15:35         ` Chris Mason
2013-03-07 15:40           ` Swâmi Petaramesh
2013-03-07 18:06         ` Jérôme Poulin
2013-03-07 18:10           ` Swâmi Petaramesh
2013-03-07 21:38             ` Mitch Harder
2013-03-07 14:13 ` Anand Jain

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=5138AE96.3020304@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Anand.Jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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.