From: Eryu Guan <guaneryu@gmail.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs-progs: canonicalize dm device name before update kernel
Date: Tue, 2 Sep 2014 20:22:53 +0800 [thread overview]
Message-ID: <20140902122253.GD3013@dhcp-13-216.nay.redhat.com> (raw)
In-Reply-To: <20140902113234.GE5888@twin.jikos.cz>
On Tue, Sep 02, 2014 at 01:32:34PM +0200, David Sterba wrote:
> On Thu, Aug 14, 2014 at 07:40:20PM +0800, Eryu Guan wrote:
> > [root@hp-dl388eg8-01 btrfs-progs]# btrfs fi show
> > Label: none uuid: 1aba7da5-ce2b-4af0-a716-db732abc60b2
> > Total devices 1 FS bytes used 384.00KiB
> > devid 1 size 15.00GiB used 2.04GiB path /dev/mapper/rhel_hp--dl388eg8--01-testlv1
> >
> > Label: none uuid: 26ff4f12-f6d9-4cbc-aae2-57febeefde37
> > Total devices 2 FS bytes used 112.00KiB
> > devid 1 size 15.00GiB used 2.03GiB path /dev/mapper/rhel_hp--dl388eg8--01-testlv2
> > devid 2 size 15.00GiB used 2.01GiB path /dev/mapper/rhel_hp--dl388eg8--01-testlv3
> >
> > Btrfs v3.14.2
>
> The commit b276e4bc50b6ca99056a45315ea859c68d58fc1b
> "canonicalize pathnames for device commands" supposedly fixes the same
> problem, added in 3.16. Can you please test that it works in your case
> as well? Thanks.
Yes, confirmed v3.16 fixes the issue, the device name didn't change
after btrfsck and btrfs device scan -d
Thanks,
Eryu
prev parent reply other threads:[~2014-09-02 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 11:40 [PATCH 1/2 RFC] btrfs-progs: scan devices for specific fsid in btrfs_scan_for_fsid Eryu Guan
2014-08-14 11:40 ` [PATCH 2/2] btrfs-progs: canonicalize dm device name before update kernel Eryu Guan
2014-08-15 1:50 ` Anand Jain
2014-08-15 4:30 ` Eryu Guan
2014-08-20 2:59 ` Anand Jain
2014-09-02 11:32 ` David Sterba
2014-09-02 12:22 ` Eryu Guan [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=20140902122253.GD3013@dhcp-13-216.nay.redhat.com \
--to=guaneryu@gmail.com \
--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).