From: Marat Khalili <mkh@rqc.ru>
To: linux-btrfs@vger.kernel.org
Subject: Re: Encountered kernel bug#72811. Advice on recovery?
Date: Sun, 16 Apr 2017 11:01:00 +0300 [thread overview]
Message-ID: <4868ddee9604c8b5aa208580fa01b7e7@rqc.ru> (raw)
In-Reply-To: <pan$5f10d$2c1e5c86$a2062192$8e2ab6b@cox.net>
> Even making such a warning conditional on kernel version is
> problematic, because many distros backport major blocks of code,
> including perhaps btrfs fixes, and the nominally 3.14 or whatever
> kernel may actually be running btrfs and other fixes from 4.14 or
> later, by the time they actually drop support for whatever LTS distro
> version and quit backporting fixes.
This information could be stored in kernel and made available for
usermode tools via some proc file. This would be very useful
_especially_ considering backporting. Raid56 could be fixed already (or
not) by the time it is implemented, but no doubt there will still be
other highly experimental capabilities judging by how things go. And
this feature itself could easily be backported.
Some machine-readable readiness level (ok/warning/override flag
needed/known but disabled in kernel) plus one-line text message
displayed to users in cases 2-4 is all we need. If proc file is missing
or doesn't contain information about specific capability, tools could
default to current behavior (AFAIR there're already warnings in some
cases). Message should tersely cover any known issues, including
stability, performance, compatibility and general readiness, and may
contain links (to btrfs wiki?) for more information. I expect whole file
to easily fit in 512 bytes.
--
With Best Regards,
Marat Khalili
next prev parent reply other threads:[~2017-04-16 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 18:49 Encountered kernel bug#72811. Advice on recovery? Ank Ular
2017-04-14 3:47 ` Duncan
2017-04-14 16:56 ` ronnie sahlberg
2017-04-15 1:41 ` Duncan
2017-04-15 23:28 ` Duncan
2017-04-15 23:32 ` Hugo Mills
2017-04-16 8:01 ` Marat Khalili [this message]
2017-04-16 15:09 ` Duncan
2017-04-14 16:46 ` Chris Murphy
2017-04-14 16:58 ` Chris Murphy
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=4868ddee9604c8b5aa208580fa01b7e7@rqc.ru \
--to=mkh@rqc.ru \
--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.