From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: Heinz Diehl <htd+ml@fritha.org>
Cc: linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org
Subject: Re: NILFS2: double uuid
Date: Mon, 08 Jun 2015 17:18:34 +0900 [thread overview]
Message-ID: <55754FDA.10406@lab.ntt.co.jp> (raw)
In-Reply-To: <20150608064314.GA3172@fritha.org>
(CCed to linux-nilfs@vger.kernel.org)
Hi Heinz,
On 2015/06/08 15:43, Heinz Diehl wrote:
> Hi,
>
> a nilfs2 formatted disk fails to mount via fstab due to double uuid's.
> See lsblk output below. The logs indicate that the system attempts to
> mount /dev/sdb rather than /dev/sdb1, which of course fails. In
> addition, /dev/sdb should not have any uuid at all. Don't know why
> that happens.
>
> The phenomenon is easily reproducible: format a partition with nilfs2,
> register it with the proper uuid in fstab and reboot. Tried both with
> USB memory and real HDD.
>
> [root@keera ~]# lsblk -f
> NAME FSTYPE LABEL UUID MOUNTPOINT
> sdb ff17dda9-fcae-42e7-a438-9087de58902e
> `-sdb1 xfs ff17dda9-fcae-42e7-a438-9087de58902e
>
> Thanks,
> Heinz
On 2015/06/08 15:49, Heinz Diehl wrote:
> On 08.06.2015, Heinz Diehl wrote:
>
>> [root@keera ~]# lsblk -f
>> NAME FSTYPE LABEL UUID MOUNTPOINT
>> sdb ff17dda9-fcae-42e7-a438-9087de58902e
>> `-sdb1 xfs ff17dda9-fcae-42e7-a438-9087de58902e
>
> Copy error: replace xfs with nilfs2. Sorry!
I couldn't reproduce the issue (in a CentOS 7 environment).
Could you tell us the version information of distro,
lsblk, libblkid, nilfs-utils, and kernel you are using ?
The following is an example of mine:
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
└─sda1 nilfs2 9dcd01c0-2bc8-41bf-a400-8ad8755aac6a
$ lsblk --version
lsblk from util-linux 2.23.2
$ lscp -V
lscp (nilfs-utils 2.2.3)
$ rpm -q libblkid util-linux
libblkid-2.23.2-22.el7_1.x86_64
util-linux-2.23.2-22.el7_1.x86_64
$ uname -r
4.1.0-rc7
Regards,
Ryusuke Konishi
next prev parent reply other threads:[~2015-06-08 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 6:43 Heinz Diehl
2015-06-08 6:47 ` Heinz Diehl
2015-06-08 8:18 ` Ryusuke Konishi [this message]
2015-06-08 9:45 ` Heinz Diehl
2015-06-08 10:08 ` Heinz Diehl
2015-06-08 10:12 ` Heinz Diehl
2015-06-08 10:31 ` Ryusuke Konishi
2015-06-08 15:31 ` Ryusuke Konishi
2015-06-08 17:23 ` Heinz Diehl
2015-06-09 5:45 ` Heinz Diehl
2015-06-09 8:53 ` Karel Zak
2015-06-09 9:46 ` Heinz Diehl
2015-06-09 13:04 ` Ryusuke Konishi
2015-06-09 14:07 ` Karel Zak
2015-06-09 16:00 ` Ryusuke Konishi
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=55754FDA.10406@lab.ntt.co.jp \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=htd+ml@fritha.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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
all inboxes | Powered by JetHome®