From: David Sterba <dsterba@suse.cz>
To: Hans van Kranenburg <hans@knorrie.org>
Cc: dsterba@suse.cz, Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] btrfs: pass checksum type via BTRFS_IOC_FS_INFO ioctl
Date: Tue, 30 Jun 2020 10:48:15 +0200 [thread overview]
Message-ID: <20200630084815.GU27795@twin.jikos.cz> (raw)
In-Reply-To: <b43e807b-97f8-3b46-b29d-46318398a215@knorrie.org>
On Sun, Jun 28, 2020 at 12:35:27AM +0200, Hans van Kranenburg wrote:
> So, the same thing as done here could be done when extending
> GET_DEV_STATS because I see users are asking about counters for repaired
> errors to be added, so they can be used for early warning alerts of
> failing disks.
Yes the dev stats are extensible following the same scheme and we'll add
new counters eventually.
next prev parent reply other threads:[~2020-06-30 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 15:01 [PATCH v3] btrfs: pass checksum type via BTRFS_IOC_FS_INFO ioctl Johannes Thumshirn
2020-06-26 20:06 ` David Sterba
2020-06-27 21:01 ` Hans van Kranenburg
2020-06-27 22:35 ` Hans van Kranenburg
2020-06-29 6:45 ` Johannes Thumshirn
2020-06-30 8:48 ` David Sterba [this message]
2020-06-30 8:50 ` David Sterba
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=20200630084815.GU27795@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=hans@knorrie.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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 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).