From: Miao Xie <miaox@cn.fujitsu.com>
To: "Yan, Zheng" <zheng.yan@oracle.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [BUG] btrfs hangup when we run the "sync" command
Date: Thu, 15 Jul 2010 17:07:07 +0800 [thread overview]
Message-ID: <4C3ECFBB.40006@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTinkuiT9tBiALkCIDMs9d9J9FT9sl9GEyRogq09S@mail.gmail.com>
On Thu Jul 15 2010 16:14:31 GMT+0800 (CST), Yan, Zheng wrote:
> 2010/7/15 Miao Xie<miaox@cn.fujitsu.com>:
>> Hi, everyone
>>
>> I found btrfs will hangup when we run the sync command on my
>> x86_64 box.
>>
>> The reproduce steps is following:
>> # mkfs.btrfs -s 8192 -l 8192 -n 8192 /dev/sda1
>> # mount /dev/sda1 /mnt
>> # echo 1234567> /mnt/aaa
>> # sync
>> (btrfs hangs up)
>>
>> It seems that the btrfs doesn't support the sectorsize which is
>> greater than the page size just like ext2/3/4, though we can use
>> mkfs.btrfs to make a filesystem with a big sectorsize. Am I right?
>>
>> If yes, we must do more check in the mkfs.btrfs.
>>
>
> yes, btrfs doesn't support the sectorsize> PAGE_size.
>
So we must do more check in the mkfs.btrfs to avoid misuse, and I'll
add some check of the sectorsize into the mkfs.btrfs.
BTW, I sent some patches to the btrfs community recently, but I haven't received
any reply. Could you review them for me? though I have tested them and everything
works well.
[PATCH 1/2] btrfs: restructure try_release_extent_buffer()
[PATCH 2/2] btrfs: fix oops when leafsize is greator than nodesize
[PATCH] btrfs-progs: fix wrong extent buffer size when reading tree block
Thanks
Miao Xie
next prev parent reply other threads:[~2010-07-15 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 3:18 [BUG] btrfs hangup when we run the "sync" command Miao Xie
2010-07-15 8:14 ` Yan, Zheng
2010-07-15 9:07 ` Miao Xie [this message]
2010-07-15 16:12 ` Chris Mason
2010-07-19 1:56 ` Miao Xie
2010-07-19 2:01 ` Yan, Zheng
2010-07-19 6:17 ` Miao Xie
2010-07-19 6:46 ` Yan, Zheng
2010-07-19 8:29 ` Miao Xie
2010-07-21 12:36 ` Hubert Kario
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=4C3ECFBB.40006@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zheng.yan@oracle.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;
as well as URLs for NNTP newsgroup(s).