From the log I can see that the disk that is named /dev/sdb during installation
gets named /dev/sde after first reboot. Since the device name used in
/etc/cryptotab
is /dev/disk/by-id/ata-WDC_WD10EARS-00MVWB0_WD-WMAZ20392365-part1all is still
working fine but it is confusing that the name if the dm table used for
encryption
is "cr_sdb1". I use this name intentionally since normally it should point
users to the
https://bugzilla.novell.com/show_bug.cgi?id=760213
https://bugzilla.novell.com/show_bug.cgi?id=760213#c6
Thomas Fehr changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fehr@suse.com
AssignedTo|fehr@suse.com |kernel-maintainers@forge.pr
| |ovo.novell.com
--- Comment #6 from Thomas Fehr 2012-05-14 10:07:38 UTC ---
the partition that is used by the dm map. Of course this is no help if disk
names
change. An alternative would be using e.g.
"cr_ata-WDC_WD10EARS-00MVWB0_WD-WMAZ20392365-part1" as name of the dm map
but I think most people would find that more confusing. Mostly disk names stay
stable.
So I would prefer to stay with the current naming scheme for crypto dm maps.
Question is why kernel sees the disk as /dev/sdb in installation environment
but as
/dev/sde in installed system. Such cases should not happen.
Reassigning to kernel people.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.