https://bugzilla.novell.com/show_bug.cgi?id=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c11 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|xwhu@novell.com | --- Comment #11 from Xinwei Hu <xwhu@novell.com> 2010-10-11 09:13:12 UTC --- (In reply to comment #10)
(In reply to comment #9)
(In reply to comment #8)
Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used here.
The linear mapping is created by kpartx, and partition number is part of the DM_NAME as implied with "kpartx -p_part". DM_PART is extracted from DM_NAME by kpartx_id as far as I understand.
So, in short, the logic needs some changing.
Thanks.
When it was changed? and as you see output in comment #5 DM_NAME doesn't have partition number as part of it ( It will be much easier for me if it had it)
OK. We are referring to the different $DM_NAME then. The initial $DM_NAME was got via 'dmsetup export', and it is the full table name, which includes "_part" suffix. # dmsetup export -j 253 -m 1 DM_NAME=3600508b400105b5a00015000001b0000_part1 DM_UUID=part1-mpath-3600508b400105b5a00015000001b0000 DM_STATE=ACTIVE DM_TABLE_STATE=LIVE DM_OPENCOUNT=1 DM_LAST_EVENT_NR=0 DM_MAJOR=253 DM_MINOR=1 DM_TARGET_COUNT=1 DM_TARGET_TYPES=linear DM_DEPS=1 And then, it was changed via kpartx_id, when DM_UUID was begin with "partX-". That's what you see in comment #5. Can you describe how GRUB::GetKernelDevice works? -- 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.