All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Adam Borowski <kilobyte@angband.pl>
Cc: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
	linux-btrfs@vger.kernel.org, bo.li.liu@oracle.com
Subject: Re: [PATCH v3] btrfs: fiemap: Cache and merge fiemap extent before submit it to user
Date: Sat, 17 Jun 2017 21:28:30 +0800	[thread overview]
Message-ID: <48fbf1c1-6b7b-a886-2355-bac5ec3f79ba@gmx.com> (raw)
In-Reply-To: <20170617083058.7z67mw4622oa7ajo@angband.pl>



On 2017年06月17日 16:30, Adam Borowski wrote:
> On Sat, Jun 17, 2017 at 03:43:18PM +0800, Qu Wenruo wrote:
>> On 2017年06月16日 20:33, David Sterba wrote:
>>> I see a lot of warnings from btrfs/094
>>>
>>> [13458.628334] BTRFS warning (device sdb6): unhandled fiemap cache detected: offset=581632 phys=13078528 len=4096 flags=0x800
>>
>> Strangely, I can't reproduce it either on my original branch (v4.12 with
>> this patch), or torvalds/master (this patch is already merged with your
>> renaming)
> 
> I for one get this a lot even in regular use.  Somehow, it always has Comm:
> dpkg, despite the vast majority of activity on the system obviously not
> being dpkg.

Is that with 0x800 flag? Or some other flag?
I'm trying fallocated file with my original branch, but still no chance 
to reproduce it though.

> 
>> However I tried all btrfs/09*,  nothing happened.
>>
>> Is some other out-of-tree patch causing the problem?
>> If so, which branch are you testing? I think I could help to fix it.
> 
> For me, linus/master with a handful of not possibly relevant patches
> (in fs/btrfs/ I have dedupe and defrag on files opened ro, raid5/6 warning,
> raid5/6 incompat flag clearing).

linus/master without any extra patch is still the same?
And which commit?
I'm using 1439ccf73d9c07654fdd5b4969fd53c2feb8684d, at least it doesn't 
cause any warning the related test case, and I tried several combination 
with preallocated and written and hole, still no chance.

I also ran btrfs/* with my patch applied on v4.11-rc2 (sorry, that's the 
correct original patch base), and except some known bug, it doesn't 
cause anything special.

Thanks,
Qu

> 
> 
> Meow!
> 

  reply	other threads:[~2017-06-17 13:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  2:43 [PATCH v3] btrfs: fiemap: Cache and merge fiemap extent before submit it to user Qu Wenruo
2017-04-12 15:05 ` David Sterba
2017-04-13  0:36   ` Qu Wenruo
2017-05-05 17:41     ` David Sterba
2017-04-20  1:25 ` Liu Bo
2017-04-20  1:52   ` Qu Wenruo
2017-04-20  1:58     ` Liu Bo
2017-04-20  2:09       ` Qu Wenruo
2017-04-20 19:52         ` Liu Bo
2017-05-05 17:38           ` David Sterba
2017-05-05 17:36         ` David Sterba
2017-04-20  2:08     ` Liu Bo
2017-04-20  2:16       ` Qu Wenruo
2017-06-16 12:33 ` David Sterba
2017-06-17  7:43   ` Qu Wenruo
2017-06-17  8:30     ` Adam Borowski
2017-06-17 13:28       ` Qu Wenruo [this message]
2017-06-17 14:57         ` Adam Borowski
2017-06-17 21:24         ` Adam Borowski
2017-06-18  9:38           ` Qu Wenruo
2017-06-18 11:23             ` Qu Wenruo
2017-06-18 11:56               ` Holger Hoffstätte
2017-06-18 13:42               ` Adam Borowski
2017-06-21  8:13                 ` Qu Wenruo

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=48fbf1c1-6b7b-a886-2355-bac5ec3f79ba@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=kilobyte@angband.pl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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 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.