From: Arne Jansen <sensille@gmx.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
Date: Tue, 24 Jan 2012 10:28:11 +0100 [thread overview]
Message-ID: <4F1E79AB.10206@gmx.net> (raw)
In-Reply-To: <201201211149.53403.Martin@lichtvoll.de>
On 21.01.2012 11:49, Martin Steigerwald wrote:
> Am Dienstag, 20. Dezember 2011 schrieb Martin Steigerwald:
>
> When I do btrfs scrub start / the machine locks immediately up hard.
Can you please give me the output of sysrq-w when the machine is locked up?
Thanks,
Arne
>
> 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.
>
> When I then boot with 3.1 it works. BTRFS redos the space_cache then while
> the machine takes ages to boot - I mean ages - 10 minutes till KDM prompt
> 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
> 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
> Intel SSD 320 and one 2,5 inch external drive as well as a 3,5 inch
> external backup drive both via eSATA, so this seems to be no principal
> issue. It also works on a workstation at work which has 32-bit debian as
> well.
>
> Thanks,
next prev parent reply other threads:[~2012-01-24 9:28 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
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 [this message]
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=4F1E79AB.10206@gmx.net \
--to=sensille@gmx.net \
--cc=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).