From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel got struck while scrubbing BTRFS with node- and leafsize 32768
Date: Sat, 16 Jun 2012 22:38:23 +0200 [thread overview]
Message-ID: <201206162238.23317.Martin@lichtvoll.de> (raw)
In-Reply-To: <201206162223.20392.Martin@lichtvoll.de>
Am Samstag, 16. Juni 2012 schrieb Martin Steigerwald:
> merkaba:~> date ; btrfs scrub status /mnt/amazon-daten
> Sa 16. Jun 22:06:33 CEST 2012
> scrub status for bd94ea73-6e77-4c81-b053-2401b4f52b3e
> scrub started at Sat Jun 16 21:44:09 2012, running for 1341
> seconds total bytes scrubbed: 90.30GB with 0 errors
> merkaba:~> date ; btrfs scrub cancel /mnt/amazon-daten
> Sa 16. Jun 22:06:47 CEST 2012
> [… hangs here …]
btrfs-readahead is stuck:
merkaba:~> ps aux | egrep "(USER| D)"
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 11920 0.0 0.0 0 0 ? D 21:46 0:00 [btrfs-readahead]
root 13649 0.0 0.0 10544 396 pts/0 D+ 22:06 0:00 btrfs scrub cancel /mnt/amazon-daten
root 16309 0.0 0.0 9816 948 pts/1 S+ 22:24 0:00 egrep (USER| D)
I created a bug report with a
kern.log including echo t > /proc/sysrq-trigger with stuck readahead
I will no be redoing the backup drive as 4K node and leaf size.
The production one I will leave at 32K for now, so I might be able to
reproduce this hang.
But first checksum error free redundancy minus the few affected files
that are not that important to me.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-06-16 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 20:23 kernel got struck while scrubbing BTRFS with node- and leafsize 32768 Martin Steigerwald
2012-06-16 20:38 ` Martin Steigerwald [this message]
2012-06-16 20:39 ` Martin Steigerwald
2012-06-24 15:02 ` Martin Steigerwald
2012-06-17 8:52 ` Martin Steigerwald
2012-06-25 3:27 ` Chester
2012-06-25 7:14 ` 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=201206162238.23317.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.