All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Pook <slp644161@pook.it>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: uncorrectable errors after btrfs replace
Date: Mon, 26 Aug 2013 00:10:13 +0200	[thread overview]
Message-ID: <521A80C5.70208@pook.it> (raw)
In-Reply-To: <52138852.3080605@giantdisaster.de>

On 20/08/13 17:16, Stefan Behrens wrote:

> I spent my whole day yesterday to check the replace procedure for errors
> by doing similar things like you did, including inserting write errors,
> using LUKS and everything.

thanks

> The only issue that I was able to find was
> that it is not checked whether the filesystem is in read-only mode when
> the operation starts.

Note that I started the replace and then set the filesystem to readonly.  The replace then stopped.  I set the filesystem back to readwrite and restarted the replace.

> Therefore I'm looking forward to read
> through your kernel log files.

I emailed them to Stefan Behrens & Chris Murphy.  Please let me know if you did not get them (presumably because they are too big).

Stuart

  reply	other threads:[~2013-08-25 22:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1753593Ab3HRQvp/20130818165145Z+301@vger.kernel.org>
2013-08-18 19:12 ` uncorrectable errors after btrfs replace Stuart Pook
2013-08-18 21:43   ` Chris Murphy
2013-08-18 22:35     ` Stuart Pook
2013-08-19  0:42       ` Chris Murphy
2013-08-19  1:21         ` George Mitchell
2013-08-20 14:46         ` slp644161
2013-08-20 15:16           ` Stefan Behrens
2013-08-25 22:10             ` Stuart Pook [this message]
2013-08-26  2:07               ` Chris Murphy
2013-08-26  2:32                 ` Chris Murphy
2013-09-02 16:23                 ` Stefan Behrens
2013-08-20  9:44       ` Stefan Behrens
2013-08-20 13:52         ` slp644161
2013-08-20 14:50           ` Stefan Behrens

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=521A80C5.70208@pook.it \
    --to=slp644161@pook.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=sbehrens@giantdisaster.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 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.