From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org, helmut@hullen.de
Subject: Re: "scrub" stops the machine
Date: Mon, 19 Mar 2012 09:22:58 +0100 [thread overview]
Message-ID: <201203190922.58586.Martin@lichtvoll.de> (raw)
In-Reply-To: <C52rKdGT1uB@helmut.hullen.de>
Am Samstag, 17. M=E4rz 2012 schrieb Helmut Hullen:
> Du meintest am 17.03.12:
> >>>> btrfs scrub start /mnt/btr
> >>>>=20
> >>>> and all was dead. Really dead. No access via keybord, no access
> >>>> via SSH.
>=20
> Kernel 3.2.9
>=20
> [...]
>=20
> > Please review the thread I started with subject:
> >=20
> > 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
>=20
> Your system has run for some seconds and has sent messages. My syste
> seems to die immediately after receiving "scrub start".
Initially mine did as well as I wrote in the initial posting.
Then possibly after some kernel upgrade, I did a btrfs filesystem balan=
ce=20
on it and then the scrub didn=B4t die immediately, but got stuck. Did y=
ou=20
try whether a balance works?
Maybe 3.2.10 oder 3.2.11 contains some related fixes? But then I don=B4=
t=20
think that the Debian Wheezy kernel already has 3.2.10 or 3.2.11.
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 8:22 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 [this message]
2012-03-19 11:00 ` Chris Samuel
2012-03-19 17:10 ` Martin Steigerwald
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=201203190922.58586.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=helmut@hullen.de \
--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.