From: Martin Steigerwald <Martin@lichtvoll.de>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel got struck while scrubbing BTRFS with node- and leafsize 32768
Date: Mon, 25 Jun 2012 09:14:20 +0200 [thread overview]
Message-ID: <201206250914.21256.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAAE6i0hruv7t-cXCbGwCvqsVW2AfBnvEbrZUf4=YraHBgsgYVQ@mail.gmail.com>
Am Montag, 25. Juni 2012 schrieb Chester:
> On Sat, Jun 16, 2012 at 3:23 PM, Martin Steigerwald
<Martin@lichtvoll.de> wrote:
> > [251818.022631] ------------[ cut here ]------------
> > [251818.022714] WARNING: at
> >
> > /media/data/mattems/src/linux-2.6-3.4.1/debian/build/source_amd64_non
> > e/fs/btrfs/extent_io.c:4522 read_extent_buffer+0x43/0xf0 [btrfs]()
> > [251818.022723] Hardware name: 42433WG
> > [251818.022727] Modules linked in: rose usb_storage uas rfcomm bnep
> > btusb
>
> I don't think btrfs supported big blocks until recently. Something
> like 3.3 or 3.4.. Anything from 2.6 would definitely not cut it.
As I reported I was using 3.4.
AFAIK it needs 3.4 for big metadata blocks.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2012-06-25 7:14 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
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 [this message]
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=201206250914.21256.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.com \
/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