Skip to contentSkip to conversation

output from "blkid" unstable (util-linux 2.22.2)

DISCUSSION Andreas Hofmeister 2 participants 4 messages Jan 28, 2013 – Feb 2, 2013 Util-Linux package

lore
Share & tools
lore

Andreas Hofmeister

author
#0 lore raw

Hi,

my "/dev/sdc" is LVM PV and "bkid says so - sometimes:

---8<---

root@ai:~# blkid /dev/sdc
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID=",,," TYPE="LVM2_member"
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID="..." TYPE="LVM2_member"
root@ai:~# blkid /dev/sdc
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID="..." TYPE="LVM2_member"
,,,
--->8---

When looking at "blkid.tab" after each blkid invocation, it seems a record for "/dev/sdc" is added and then is removed again.

"blkid" from 2.21 did not have that problem, and a git bisect revealed commit 2b29c1bfca6e52c9c1ce2e41fde7967c150c5877 as the culprit.

Reverting that commit made "blkid.tab" and "blkid" output stable.

Ciao
Andi

maintainer
#1 lore raw
Quoted 12 lines · Andreas Hofmeister

---8<---

root@ai:~# blkid /dev/sdc
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID=",,," TYPE="LVM2_member"
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID="..." TYPE="LVM2_member"
root@ai:~# blkid /dev/sdc
root@ai:~# blkid /dev/sdc
/dev/sdc: UUID="..." TYPE="LVM2_member"
,,,
--->8---

Probably fixed in our git three.

Andreas, please try:

git clone git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
cd util-linux
./autogen.sh
./configure
make blkid

  # ./blkid /dev/sdc

Karel

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com
maintainer
#2 lore raw
Quoted 1 line · Karel Zak

Probably fixed in our git three.

ops... s/three/tree/ ;-)

Karel

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com
author Applied
#3 lore raw
In reply to Karel Zak
Quoted 2 lines · Karel Zak

cd util-linux
./autogen.sh

Had a bit if a problem with my auto-tools, so I could not actually check "master"

But apparently you found the problem already :-)

I applied your commit 6a0766444dc4f1b23b1f0da9c380fb1ced0bfb0a onto the sources from the v2.22.2 tar archive. So far, that seems to have fixed the problem.

Thanks
Andi