From: David Sterba <dsterba@suse.cz>
To: Mike Fleetwood <mike.fleetwood@googlemail.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Add dev uuid output for print_dev_item().
Date: Mon, 2 Jun 2014 19:43:18 +0200 [thread overview]
Message-ID: <20140602174318.GF22324@twin.jikos.cz> (raw)
In-Reply-To: <CAMU1PDhBuk46VgwNVnO_1JzOgZka1wd8dMvTjECwTRBsfZeghQ@mail.gmail.com>
On Thu, May 29, 2014 at 08:52:04PM +0100, Mike Fleetwood wrote:
> On 29 May 2014 02:02, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
> > The original print_dev_item() only prints device id,total bytes and
> > bytes used.
> > When it comes to debug things related to duplicated device id, dev uuid
> > is needed to distinguish different device since device is is no
> > reliable.
>
> At the end of the message I think there is a couple of typos and you meant:
> ... device id is not reliable.
Fixed, thanks.
prev parent reply other threads:[~2014-06-02 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 1:02 [PATCH] btrfs-progs: Add dev uuid output for print_dev_item() Qu Wenruo
2014-05-29 19:52 ` Mike Fleetwood
2014-05-30 0:58 ` Qu Wenruo
2014-06-02 17:43 ` 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=20140602174318.GF22324@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mike.fleetwood@googlemail.com \
--cc=quwenruo@cn.fujitsu.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).