From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] [btrfs] add volid to failed csum messages
Date: Tue, 20 May 2014 23:10:02 +0000 (UTC) [thread overview]
Message-ID: <pan$c54e$df2621e8$4265fcce$f42580ef@cox.net> (raw)
In-Reply-To: orsio41mxo.fsf@free.home
Alexandre Oliva posted on Tue, 20 May 2014 12:37:07 -0300 as excerpted:
> The failed csum messages generated by btrfs mention the inode number,
> but on filesystems with multiple subvolumes, that's not enough to
> identify the file. I've added the inode number to the messages
?? s/added the inode number/added the volid/ ??
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-05-20 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 15:37 [PATCH] [btrfs] add volid to failed csum messages Alexandre Oliva
2014-05-20 23:10 ` Duncan [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='pan$c54e$df2621e8$4265fcce$f42580ef@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).