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: Sat, 21 Jan 2012 11:49:53 +0100 [thread overview]
Message-ID: <201201211149.53403.Martin@lichtvoll.de> (raw)
In-Reply-To: <201112202146.32265.Martin@lichtvoll.de>
Am Dienstag, 20. Dezember 2011 schrieb Martin Steigerwald:
> Hi again!
[=E2=80=A6]
> Am Samstag, 17. Dezember 2011 schrieb Martin Steigerwald:
> > Hi!
> >=20
> > Finally I tried scrubbing the / BTRFS filesystem mentioned in the
> > thread "speeding up slow btrfs filesystem". However the machine loo=
ks
> > up hard then. It repeats the last few seconds of audio all over
> > again, no mouse and no ssh connection anymore:
> >=20
> > deepdance:~> btrfs scrub start /
> > scrub started on /, fsid [=E2=80=A6] (pid=3D5737)
> > deepdance:~> Write failed: Broken pipe
> >=20
> >=20
> > After the second attempt of doing this the machine stops on booting
> > after the space cache enabled message. Then I get backtraced of hun=
g
> > tasks:
> >=20
> > http://martin-steigerwald.de/tmp/btrfs/2011-17-12-deepdance-hang-at=
-b
> > oot/
> >=20
> >=20
> > I am able to mount the filesystem from grml 2011.12-rc1 with 3.1
> > kernel:
I still have this with 3.2.0-1-pae - which is a debian kernel based on=20
3.2.1.
When I do btrfs scrub start / the machine locks immediately up hard.
Then usually on next boot it stops on space_cache enabled message, but =
not=20
the one for /, but the one for /home which is mounted later.
When I then boot with 3.1 it works. BTRFS redos the space_cache then wh=
ile=20
the machine takes ages to boot - I mean ages - 10 minutes till KDM prom=
pt=20
is no problem there.
I thought I just mention it here.
Since I got no hints on what to do, I probably redo both filesystems on=
the=20
machine. Should that not work out, I switch the box to Ext4.
btrfs filesystem scrub works on my ThinkPad T520 with 64-bit debian and=
=20
Intel SSD 320 and one 2,5 inch external drive as well as a 3,5 inch=20
external backup drive both via eSATA, so this seems to be no principal=20
issue. It also works on a workstation at work which has 32-bit debian a=
s=20
well.
Thanks,
--=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-01-21 10:49 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 [this message]
2012-01-21 11:19 ` Martin Steigerwald
2012-02-24 15:51 ` Martin Steigerwald
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=201201211149.53403.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 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).