From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Daniel J Blueman <daniel@quora.org>
Cc: Chris Mason <chris.mason@oracle.com>,
Linux BTRFS <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@redhat.com>
Subject: Re: btrfs_search_slot BUG...
Date: Fri, 09 Mar 2012 12:34:01 +0800 [thread overview]
Message-ID: <4F598839.5060806@cn.fujitsu.com> (raw)
In-Reply-To: <CAMVG2suFfpjC_n8SpaDRLAZpWGFAPdoT+ESOkrNuoH0WoH8juQ@mail.gmail.com>
On 03/09/2012 12:25 PM, Daniel J Blueman wrote:
> When testing out 16KB blocks with direct I/O [1] on 3.3-rc6, we
> quickly see btrfs_search_slot returning positive numbers, popping an
> assertion [2].
>
> Are >4KB block sizes known broken for now?
>
Yes, exactly, the kernel side is not ready for >4K block size, but AFAIK it _is_ on going.
thanks,
liubo
> Thanks,
> Daniel
>
> --- [1]
>
> mkfs.btrfs -m raid1 -d raid1 -l 16k -n 16k /dev/sda /dev/sdb
> mount /dev/sda /store && cd /store
> fio /usr/share/doc/fio/examples/iometer-file-access-server
>
> --- [2]
>
> kernel BUG at /home/apw/COD/linux/fs/btrfs/extent-tree.c:1481!
next prev parent reply other threads:[~2012-03-09 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 4:25 btrfs_search_slot BUG Daniel J Blueman
2012-03-09 4:34 ` Liu Bo [this message]
2012-03-09 14:01 ` David Sterba
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=4F598839.5060806@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=daniel@quora.org \
--cc=josef@redhat.com \
--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).