linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: "Jakob Schürz" <wertstoffe@nurfuerspam.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-balance causes system-freeze on full disk
Date: Tue, 27 Oct 2015 17:09:04 +0000	[thread overview]
Message-ID: <20151027170904.GK11331@carfax.org.uk> (raw)
In-Reply-To: <40k4gc-scp.ln1@aldebaran.xundeenergie.at>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

On Tue, Oct 27, 2015 at 05:05:55PM +0100, Jakob Schürz wrote:
> Found a new habit...
> 
> I have a lot Snapshots on my drive. (Take every 10 Min a new one, every
> houry one, every day one, every system-update, every plugin after
> external HD...)
> 
> If there are to much snapshots (didn't find out the count how much
> exactly) balancing fails with a system-freeze.
> if i delete some of my snapshots, balancing is working...

   The whole machine comes to a halt, or just the balancing? If you
have lots of snapshots, balance can take *insane* amounts of time --
my big storage array, for example, takes about 60 seconds to balance a
data block group, and something like 4+ hours to balance some of the
metadata block groups. While it's "stuck" like that, it is actually
making progress, but it doesn't look like it.

   Hugo.

> Maybe this is a hint for bugfixing!!
> 
> Do you think?
> 
> greez
> 
> Jakob
> 
> Am 2015-10-21 um 22:51 schrieb Kyle Manna:
> > I had a number of similar btrfs balance crashes in the past few days,
> > but the disk wasn't full.  You should try tailing the system logs from
> > a remote machine when it happens. You'll likely see some bug info
> > before the system dies and becomes unusable.
> > 
> > The issue I encountered is described @
> > https://bugzilla.kernel.org/show_bug.cgi?id=105681
> > ᐧ
> > 
> > On Wed, Oct 21, 2015 at 12:38 PM, Jakob Schürz
> > <wertstoffe@nurfuerspam.de> wrote:
> >> Hi there!
> >>
> >> Is it possible, what i've recognized now. My system (debian) runs on
> >> btrfs, and i have a lot of snapshots on my hard-disk.
> >> Since some days my system freezes totally. I recognized, it always
> >> happens during btrfs-balance.
> >>
> >> So i deleted some of the old snapshots and tried another balance-run.
> >> Nothing happened... No system-freeze.
> >>
> >> System-freeze means: No Keyboard-action. The Mouse is frozen, the screen
> >> is frozen, no magic-sysreq, no ssh-login.
> >>
> >> Can btrfs cause such a freeze??
> >>
> >> greez
> >>
> >> jakob

-- 
Hugo Mills             | Darkling's First Law of Filesystems:
hugo@... carfax.org.uk | The user hates their data
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2015-10-27 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 19:38 btrfs-balance causes system-freeze on full disk Jakob Schürz
2015-10-21 20:51 ` Kyle Manna
2015-10-21 21:04   ` Jakob Schürz
2015-10-22  3:34   ` Duncan
2015-10-27 16:05   ` Jakob Schürz
2015-10-27 17:09     ` Filipe Manana
2015-10-27 17:09     ` Hugo Mills [this message]
2015-10-27 18:23       ` Jakob Schürz

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=20151027170904.GK11331@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wertstoffe@nurfuerspam.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;
as well as URLs for NNTP newsgroup(s).