public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: "Mr. Tux" <tuxoholic@hotmail.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Howto mount intact left-over device of a degraded btrfs-raid?
Date: Tue, 26 Jan 2010 21:12:49 -0500	[thread overview]
Message-ID: <20100127021249.GD11767@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <BLU0-SMTP1013A688BD201E681FCA798D85E0@phx.gbl>

On Tue, Jan 26, 2010 at 01:20:30PM +0100, Mr. Tux wrote:
> On Monday 25 January 2010 23:08:39 Josef Bacik wrote:
> 
> Hi Josef
> 
> >
> > Hmm well I'm trying to reproduce that here and it's working fine, course I
> > can't pull a cable on my disk since I only have one disk to test with. 
> > Would you mind sending me your dmesg after you try
> >
> > mount -o degraded /dev/sda1 /mnt/
> >
> > so I can see whats going on.  Thanks,
> >
> 
> Did you try 2.6.32.2 from kernel.org? Is it possible to use  a second test 
> drive like I did? I know you can create a raid array with one device missing, 
> but the segfault happened with a two member raid1.
> 
> I don't have the test environment any more, so I can't offer a backtrace right 
> now - but I will set it up again in the next few days. If it happens again I 
> will contact you and send you a backtrace.
>

Ok I think I've tracked down all the various problems that you were having with
this.  I've sent 3 patches to the list just now

Btrfs: check total number of devices when removing missing
Btrfs: check return value of open_bdev_exclusive properly
Btrfs: do not mark the chunk as readonly if in degraded mode

Make sure you run btrfsctl -a before running mount -o degraded.  I made that
mistake and things still didnt work.  Let me know if you have any problems.
Thanks,

Josef 

      reply	other threads:[~2010-01-27  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 18:31 Howto mount intact left-over device of a degraded btrfs-raid? Mr. Tux
2010-01-25 18:43 ` Josef Bacik
2010-01-25 21:46   ` Mr. Tux
2010-01-25 22:08     ` Josef Bacik
2010-01-26 12:20       ` Mr. Tux
2010-01-27  2:12         ` Josef Bacik [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=20100127021249.GD11767@dhcp231-156.rdu.redhat.com \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tuxoholic@hotmail.de \
    /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