All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: hard lockup while balance was running killed my raid5
Date: Tue, 5 May 2015 17:03:19 +0000 (UTC)	[thread overview]
Message-ID: <pan.2015.05.05.17.03.19@googlemail.com> (raw)
In-Reply-To: 5548F177.1040309@linuxmail.org

On Tue, 05 May 2015 11:36:07 -0500, Perry Gilfillan wrote:

> My kernel
> Linux lightmyfire 4.1.0-0.rc1.git1.1.fc23.x86_64 #1 SMP Sun May 3 
> 14:26:14 CDT 2015 x86_64 x86_64 x86_64 GNU/Linux
> 
> I've got btrfs-progs and btrfs-progs-unstable from git, so I'll use 
> which ever might be useful for any further diagnostics.
> 
> Since devid 1 & 2 appear to be fully utilized, I set off a balance, the 
> system locked up,  and nothing I've read points to a solution yet.

I've also had a hard lockup just the other day during a balance (on a
single device though), so this points to some changes in the 4.1 merge
window.

Just to confirm: by "hard lockup" you mean that the entire box is frozen,
no longer shows any signs of life and no longer responds to anything?

One thing you could try is to mount your devices without the free-space
cache (-o clear_cache,nospace_cache) and try to run the balance.

Would be interesting to see if that helps.

-h


  reply	other threads:[~2015-05-05 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 16:36 hard lockup while balance was running killed my raid5 Perry Gilfillan
2015-05-05 17:03 ` Holger Hoffstätte [this message]
2015-05-05 18:06   ` Perry Gilfillan
2015-05-06  3:46     ` ronnie sahlberg
2015-05-06  3:56       ` Chris Murphy
2015-05-07 17:21     ` Perry Gilfillan
2015-05-05 17:17 ` Chris Murphy
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05  0:02 Perry Gilfillan

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=pan.2015.05.05.17.03.19@googlemail.com \
    --to=holger.hoffstaette@googlemail.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.