All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: test whether fallocate(2) can preallocate half of the whole fs space
Date: Thu, 21 Jul 2016 15:24:38 +0800	[thread overview]
Message-ID: <579078B6.2020604@cn.fujitsu.com> (raw)
In-Reply-To: <20160720190009.GA13348@infradead.org>

hello,

On 07/21/2016 03:00 AM, Christoph Hellwig wrote:
> On Wed, Jul 20, 2016 at 03:34:50PM +0800, Wang Xiaoguang wrote:
>> Currently in btrfs, there is something wrong with data space reservation.
>> For example, if we try to preallocate more than haf of whole fs space,
>> ENOSPC will occur, but indeed fs still has free space to satisfy this
>> request.
>>
>> To easily reproduce this bug, this test case needs fs is mixed mode(btrfs
>> specific), so put this test case in btrfs group, not generic group.
> But the actual test isn't btrfs specific, and other file systems might
> have issues in this area as well.  Please add it to the generic group
> instead.
OK, new version will be sent soon.
ext4 & xfs pass the test, btrfs fails.

Regards,
Xiaoguang Wang

>




      reply	other threads:[~2016-07-21  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20  7:34 [PATCH] btrfs: test whether fallocate(2) can preallocate half of the whole fs space Wang Xiaoguang
2016-07-20  9:25 ` Filipe Manana
2016-07-21  7:22   ` Wang Xiaoguang
2016-07-20 19:00 ` Christoph Hellwig
2016-07-21  7:24   ` Wang Xiaoguang [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=579078B6.2020604@cn.fujitsu.com \
    --to=wangxg.fnst@cn.fujitsu.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --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.