All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torbjørn Skagestad" <torbjorn@itpas.no>
To: dsterba@suse.cz, Torbjørn <lists@skagestad.org>,
	linux-btrfs@vger.kernel.org, chris.mason@fusionio.com
Subject: Re: Scrub causes oom after removal of failed disk (linux 3.10)
Date: Tue, 09 Jul 2013 06:15:52 +0200	[thread overview]
Message-ID: <51DB8E78.1080604@itpas.no> (raw)
In-Reply-To: <20130708213627.GG18204@twin.jikos.cz>

On 07/08/2013 11:36 PM, David Sterba wrote:
> On Wed, Jul 03, 2013 at 08:35:48PM +0200, Torbjørn wrote:
>> Hi btrfs devs,
>>
>> I have a btrfs raid10 array consisting of 2TB drives.
>>
>> I added a new drive to the array, then balanced.
>> The balance failed after ~50GB was moved to the new drive.
>> The balance fixed lots of errors according to dmesg.
>>
>> Server rebooted
>>
>> The newly added drive were no longer detected as a btrfs disk.
>> The array was then mounted -o recovery
>> I ran btrfs dev del missing, and everything seemed to be fine.
>>
>> After this I ran a scrub on the array.
>> The scrub was soon stopped by the oom-killer.
>>
>> After another reboot I started a new scrub.
>> About 3TB into the scrub over 10 GB of memory was being consumed.
>> The scrub had then fixed roughly 3,000,000 errors.
>>
>> Canceling the scrub and resuming it frees the 10 GB of memory.
> Thanks for the report.
>
> This looks like the same problem that was fixed by
> https://patchwork.kernel.org/patch/2697501/
> Btrfs: free csums when we're done scrubbing an extent
>
> but I don't see it included in the current for-linus branch. We want
> this in the 3.10.x stable series and according to stable tree policy it
> has to be merged into Linus' tree first.
>
> david
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Ok, thanks

--
Torbjørn

      reply	other threads:[~2013-07-09  4:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 18:35 Scrub causes oom after removal of failed disk (linux 3.10) Torbjørn
2013-07-08 21:36 ` David Sterba
2013-07-09  4:15   ` Torbjørn Skagestad [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=51DB8E78.1080604@itpas.no \
    --to=torbjorn@itpas.no \
    --cc=chris.mason@fusionio.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@skagestad.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.