From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#543452: ata-FUJITSU_MHT2040AT _ FUJITSU_MHT2040AT
Date: Tue, 25 Aug 2009 17:44:40 +0000 [thread overview]
Message-ID: <20090825174440.GA6204@bongo.bofh.it> (raw)
The user reports that the persistent name changes when switching from
2.6.29 to 2.6.30. Kernel bug or blkid bug?
----- Forwarded message from jidanni@jidanni.org -----
From: jidanni@jidanni.org
To: waldi@debian.org
Cc: 543452@bugs.debian.org, libsysfs2@packages.debian.org,
udev@packages.debian.org
Subject: Re: Bug#543452: ata-FUJITSU_MHT2040AT _ FUJITSU_MHT2040AT
retitle 543452 repeated names in /dev/disk/by-id
>>>>> "BB" = Bastian Blank <waldi@debian.org> writes:
BB> Please provide more information why this should be caused by
BB> libdevmapper.
Hmmm, downgrading libdevmapper1.02.1 and rebooting didn't fix it. Nor
did downgrading module-init-tools from 3.10-2 to 3.10-1. So I'm not sure
what package is at fault. Please reassign if you know.
Odd, there they are
by-id# ls -aLlog
brw-rw---- 1 3, 0 Aug 26 00:42 ata-FUJITSU_MHT2040AT_FUJITSU_MHT2040AT_NN4GT531H3AR
brw-rw---- 1 3, 1 Aug 26 00:42 ata-FUJITSU_MHT2040AT_FUJITSU_MHT2040AT_NN4GT531H3AR-part1
brw-rw---- 1 3, 3 Aug 26 00:42 ata-FUJITSU_MHT2040AT_FUJITSU_MHT2040AT_NN4GT531H3AR-part3...
But with my fstab,
by-id# mount -a
mount: special device /dev/disk/by-id/ata-FUJITSU_MHT2040AT_NN4GT531H3AR-part6 does not exist
mount: special device /dev/disk/by-id/ata-FUJITSU_MHT2040AT_NN4GT531H3AR-part7 does not exist...
This happens on both my Thinkpad and my desktop.
Wait, no wonder, comparing the strings reveals:
ata-FUJITSU_MHT2040AT_FUJITSU_MHT2040AT_NN4GT531H3AR-part3
ata-FUJITSU_MHT2040AT_NN4GT531H3AR-part3
How silly this name being repeated!
One might have thought it is related to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bugQ5598
but that is different.
I hope someone will reassign this bug to where it belongs. Thanks.
----- End forwarded message -----
--
ciao,
Marco
reply other threads:[~2009-08-25 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090825174440.GA6204@bongo.bofh.it \
--to=md@linux.it \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.