All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mario Fugazzi®" <fugazzi99@gmail.com>
To: "Janos Toth F." <toth.f.janos@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS warning: unhandled fiemap cache detected
Date: Wed, 9 Aug 2017 15:42:02 +0200	[thread overview]
Message-ID: <20170809154202.54d5ad5a@gmail.com> (raw)
In-Reply-To: <CANznX5HW86Kd21wgv9AuHgng=NQENsKKFBqUHpM0N6=b4TnEuA@mail.gmail.com>

Hi Janos, many thanks for your kind answer!
Yes, I also saw a patch regarding this for 4.13, good to know that it is not a
problem ;-)

Thank you again.
Mario


On Wed, 9 Aug 2017 13:13:08 +0200
"Janos Toth F." <toth.f.janos@gmail.com> wrote:

> As much as I can tell it's nothing to worry about. (I have thousands
> of these warnings.) I don't know why the patch was submitted for 4.13
> but not applied to the next 4.12.x , since it looks like a trivial
> tiny fix for an annoying problem.
> 
> On Wed, Aug 9, 2017 at 10:48 AM, Mario Fugazzi® <fugazzi99@gmail.com> wrote:
> > Hi everyone :-)
> >
> > After updating the kernel to the latest one 4.12 I receive a lot of
> > warnings in my dmesg but only on my ssd that is a kingston hyperx predator.
> > No message get logged for my other two traditional HD that are btrfs also.
> > Warnings show only on boot and not on every boot.
> > Kernel is now 4.12.5 but I got that till upgrading to 4.12, in 4.11 no
> > warnings.
> >
> > Just wanted to know if I have to worry about this, scrubs are ok and btrfs
> > check give me no problems.
> >
> > Thank you very much.
> > Mario.
> >
> > Some sample:
> >
> > [   13.486100] BTRFS warning (device sdd2): unhandled fiemap cache
> > detected: offset=0 phys=1960767488 len=8192 flags=0x0 [   13.486110] BTRFS
> > warning (device sdd2): unhandled fiemap cache detected: offset=0
> > phys=1960767488 len=8192 flags=0x0 [   13.486261] BTRFS warning (device
> > sdd2): unhandled fiemap cache detected: offset=0 phys=1960824832 len=12288
> > flags=0x0 [   13.486280] BTRFS warning (device sdd2): unhandled fiemap
> > cache detected: offset=0 phys=1960763392 len=4096 flags=0x0 [   13.486434]
> > BTRFS warning (device sdd2): unhandled fiemap cache detected: offset=0
> > phys=1960767488 len=8192 flags=0x0 [   13.486446] BTRFS warning (device
> > sdd2): unhandled fiemap cache detected: offset=0 phys=1960775680 len=4096
> > flags=0x0 [   13.486616] BTRFS warning (device sdd2): unhandled fiemap
> > cache detected: offset=0 phys=1960783872 len=24576 flags=0x0 [   13.486650]
> > BTRFS warning (device sdd2): unhandled fiemap cache detected: offset=0
> > phys=1960808448 len=4096 flags=0x0 [   13.486719] BTRFS warning (device
> > sdd2): unhandled fiemap cache detected: offset=0 phys=1960812544 len=8192
> > flags=0x0 [   13.486742] BTRFS warning (device sdd2): unhandled fiemap
> > cache detected: offset=0 phys=1960820736 len=4096 flags=0x0
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html  


      reply	other threads:[~2017-08-09 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  8:48 BTRFS warning: unhandled fiemap cache detected Mario Fugazzi®
2017-08-09 11:13 ` Janos Toth F.
2017-08-09 13:42   ` Mario Fugazzi® [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=20170809154202.54d5ad5a@gmail.com \
    --to=fugazzi99@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=toth.f.janos@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 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.