From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
Date: Fri, 24 Feb 2012 16:51:57 +0100 [thread overview]
Message-ID: <201202241651.57233.Martin@lichtvoll.de> (raw)
In-Reply-To: <201201211219.40433.Martin@lichtvoll.de>
Am Samstag, 21. Januar 2012 schrieb Martin Steigerwald:
> Am Samstag, 21. Januar 2012 schrieb Martin Steigerwald:
> > I still have this with 3.2.0-1-pae - which is a debian kernel based
> > on 3.2.1.
> >=20
> > When I do btrfs scrub start / the machine locks immediately up hard=
=2E
> >=20
> > Then usually on next boot it stops on space_cache enabled message,
> > but not the one for /, but the one for /home which is mounted
> > later.
> >=20
> > When I then boot with 3.1 it works. BTRFS redos the space_cache the=
n
> > while the machine takes ages to boot - I mean ages - 10 minutes ti=
ll
> > KDM prompt is no problem there.
>=20
> I now tested scrubbing /home which is a different BTRFS filesystem on
> the same machine.
>=20
> Then the scrub is started, scrub status tells me so, but nothing
> happens, no block in/out activity in vmstat, no CPU related activity
> in top.
>=20
> btrfs scrub cancel then hangs, but not the complete machine, only the
> process.
>=20
> I had this once on my T520 with the internal Intel SSD 320 as well. T=
he
> other time it worked.
>=20
> Well maybe that is due to BTRFS doing something else on my T23 now:
>=20
> deepdance:~> ps aux | grep ino-cache | grep -v grep
> root 1992 5.5 0.0 0 0 ? D 12:15 0:09
> [btrfs- ino-cache]
>=20
> Hmmm, so I just let it sit for a while, maybe eventually it will scru=
b
> /home.
>=20
> At least it doesn=C2=B4t lock up hard, so there might really be somet=
hing
> strange with /.
=46WIW a btrfs filesystem balance / does work. After this a btrfs scrub=
start=20
/ still locks the kernel.
Anyway, I might be waiting for the new fsck and try it on the partition=
=2E=20
Or redo the filesystem from scratch, cause I think trying to debug this=
=20
will take way more time.
I might also as well redo /home as well. Two fresh 3.2 or 3.3 kernel BT=
RFS=20
and see whether they work better.
--=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-02-24 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 17:33 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot Martin Steigerwald
2011-12-17 18:11 ` Martin Steigerwald
2011-12-20 20:46 ` Martin Steigerwald
2012-01-21 10:49 ` Martin Steigerwald
2012-01-21 11:19 ` Martin Steigerwald
2012-02-24 15:51 ` Martin Steigerwald [this message]
2012-02-25 8:14 ` Arne Jansen
2012-02-25 20:14 ` Martin Steigerwald
2012-03-15 17:32 ` Martin Steigerwald
2012-03-15 17:39 ` Martin Steigerwald
2012-03-15 17:42 ` Chris Mason
2012-03-15 18:03 ` Martin Steigerwald
2012-03-15 18:08 ` Chris Mason
2012-03-16 15:05 ` Martin Steigerwald
2012-03-16 15:37 ` Arne Jansen
2012-03-17 9:43 ` Martin Steigerwald
2012-03-18 0:37 ` Greg Kroah-Hartman
2012-03-19 8:31 ` Martin Steigerwald
2012-03-19 15:48 ` Greg Kroah-Hartman
2012-03-19 16:03 ` Martin Steigerwald
2012-01-24 9:28 ` Arne Jansen
2012-01-24 10:16 ` Martin Steigerwald
2012-01-24 10:29 ` Arne Jansen
2012-01-24 10:39 ` Martin Steigerwald
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=201202241651.57233.Martin@lichtvoll.de \
--to=martin@lichtvoll.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.