From: David Sterba <dsterba@suse.cz>
To: Menion <menion@gmail.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)" with 8TB HDDs
Date: Fri, 9 Mar 2018 15:54:01 +0100 [thread overview]
Message-ID: <20180309145401.GS23693@twin.jikos.cz> (raw)
In-Reply-To: <CAJVZm6eGXez164prciYkemOVVLQ+=RqfvyfB+wzW+imtxVP66w@mail.gmail.com>
On Thu, Mar 08, 2018 at 12:18:04PM +0100, Menion wrote:
> Actually this path can be taken in few occurrency
>
> 1) device probe, only when the device is plugged or detected the first time
> 2) revalidate_disk fops of block device
>
> Is it possible that BTRFS every 5 minutes call the revalidate_disk?
An idea: udev or blkid cache refresh, triggers 'btrfs dev scan' that
calls blkdev_get_by_path that could in turn call the revalidation and
whatnot.
Alternatively you can patch the code and add a WARN_ON right after the
message, the stacktrace will tell for sure from where it gets triggered.
prev parent reply other threads:[~2018-03-09 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJVZm6etk=bL0LY3FZXkm5Wun64F4w6HMxdLhKRD-v+mEGm08w@mail.gmail.com>
2018-03-02 11:37 ` dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)" with 8TB HDDs Menion
2018-03-02 15:18 ` David Sterba
2018-03-02 16:19 ` Menion
2018-03-08 10:16 ` Menion
2018-03-08 11:18 ` Menion
2018-03-09 14:54 ` David Sterba [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=20180309145401.GS23693@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=menion@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 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).