From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: Wolfgang_Mader@brain-frog.de, dsterba@suse.cz
Subject: [PATCH 0/2] serviceability: add event log when missing device is created
Date: Mon, 27 Apr 2015 12:46:17 +0800 [thread overview]
Message-ID: <1430109979-9397-1-git-send-email-anand.jain@oracle.com> (raw)
Wolfgang was in a situation that he wanted to know the device-id
of a missing device as indicated by 'btrfs fi show'
sysfs patches sent before would help. And irrespective of that,
these are system events must be logged for better pathological
analysis of the btrfs issues.
Anand Jain (2):
Btrfs: log when missing device is created
Btrfs: check error before reporting missing device and add uuid
fs/btrfs/volumes.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.0.0.153.g79dcccc
next reply other threads:[~2015-04-27 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 4:46 Anand Jain [this message]
2015-04-27 4:46 ` [PATCH 1/2] Btrfs: log when missing device is created Anand Jain
2015-05-05 15:52 ` David Sterba
2015-04-27 4:46 ` [PATCH 2/2] Btrfs: check error before reporting missing device and add uuid Anand Jain
2015-05-05 15:43 ` David Sterba
2015-05-07 20:34 ` Anand Jain
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=1430109979-9397-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=Wolfgang_Mader@brain-frog.de \
--cc=dsterba@suse.cz \
--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 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).