From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-show vs. btrfs different output
Date: 21 Mar 2013 16:33:00 +0100 [thread overview]
Message-ID: <CTGgJoCuCXB@helmut.hullen.de> (raw)
In-Reply-To: <CAKuK5J3Fd+ya3SOwQPZohJArE+cPNZKchzH3UkvpvoAnK-6Hng@mail.gmail.com>
Hallo, Jon,
Du meintest am 21.03.13:
>>> 2. the current git btrfs-show and btrfs fi show both output
>>> *different* devices for device with UUID
>>> b5dc52bd-21bf-4173-8049-d54d88c82240, and they're both wrong.
>> does blkid output find that uuid anywhere?
>> Since you're working in git, can you maybe do a little bisecting
>> to find out when it changed? Should be a fairly quick test?
> blkid does /not/ report that uuid anywhere.
"blkid" seems to be a bit clueless.
Try "file -s" instead.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2013-03-21 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 15:04 btrfs-show vs. btrfs different output Jon Nelson
2013-03-21 15:11 ` Eric Sandeen
2013-03-21 15:29 ` Jon Nelson
2013-03-21 15:33 ` Helmut Hullen [this message]
2013-03-21 16:25 ` Eric Sandeen
2013-03-22 3:06 ` Anand Jain
2013-03-22 13:59 ` Jon Nelson
2013-03-22 22:34 ` Eric Sandeen
2013-03-21 15:35 ` Helmut Hullen
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=CTGgJoCuCXB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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