From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Chris Samuel <chris@csamuel.org>
Subject: Re: "scrub" stops the machine
Date: Mon, 19 Mar 2012 18:10:19 +0100 [thread overview]
Message-ID: <201203191810.19697.Martin@lichtvoll.de> (raw)
In-Reply-To: <201203192201.04671.chris@csamuel.org>
Am Montag, 19. M=C3=A4rz 2012 schrieb Chris Samuel:
> On Monday 19 March 2012 19:22:58 Martin Steigerwald wrote:
> > Maybe 3.2.10 oder 3.2.11 contains some related fixes?
>=20
> I don't believe that any btrfs fixes get pushed to the stable release=
s
> (at least, not yet), you'll need 3.3 for newer code.
Well maybe the second btrfs filesystem balance call or a possible upgra=
de=20
of btrfs-tools fixed it for me. Cause I didn=C2=B4t do anything specifi=
c to fix=20
the hard lock up issue. The getting stuck issue Chris Mason fixed by wi=
th=20
casting patch.
Ciao,
--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
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
next prev parent reply other threads:[~2012-03-19 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F64C2D2.8030009@gmx.net>
2012-03-17 17:12 ` "scrub" stops the machine Helmut Hullen
2012-03-17 18:14 ` Martin Steigerwald
2012-03-17 18:35 ` Helmut Hullen
2012-03-19 8:22 ` Martin Steigerwald
2012-03-19 11:00 ` Chris Samuel
2012-03-19 17:10 ` Martin Steigerwald [this message]
2012-03-18 8:04 ` Helmut Hullen
2012-03-18 9:18 ` Chris Samuel
2012-03-17 16:35 Helmut Hullen
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=201203191810.19697.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=chris@csamuel.org \
--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.