Bug 606519 - /dev/mapper/pdc_efihghgip1 on / ?
/dev/mapper/pdc_efihghgip1 on / ?
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: dmraid (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: LVM and device-mapper development team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-21 16:38 EDT by Eddie Lania
Modified: 2010-06-22 03:19 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-22 03:19:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eddie Lania 2010-06-21 16:38:37 EDT
Description of problem: 

I think this is more a question then a bug.

After doing a clean install of Fedora 13 on a system with two disks in a raid1 configuration on a Fasttrak Tx2000 firmware/bios fake raid controller (yeah I know that's cheap), the file system is mounted on /dev/mapper/pdc_efihghgip1.

Is this supposed to be so?

I mean, when I look at the output of the dmevent_tool:

dmevent_tool -mu
pdc_efihghgip2 not monitored
pdc_efihghgip1 not monitored
pdc_efihghgi not monitored


I see that both disks are being displayed as pdc_efihghgip1 and pdc_efihghgip2, but what is then pdc_efihghgi ?

Is that the actual raid device? And is it not supposed to be mounted instead?

It is not clear to me how things work in this case and I searched for more information but failed to find any.



Version-Release number of selected component (if applicable):

dmraid-events-logwatch-1.0.0.rc16-12.fc13.i686
dmraid-events-1.0.0.rc16-12.fc13.i686
dmraid-1.0.0.rc16-12.fc13.i686

How reproducible: Allways


Steps to Reproduce:
1. Install F13 on fasttrak mirrored array.
2.
3.
  
Actual results: / mounted on /dev/mapper/pdc_efihghgip1


Expected results: / mounted on /dev/mapper/pdc_efihghgip ?


Additional info:
Comment 1 Hans de Goede 2010-06-22 03:19:05 EDT
(In reply to comment #0)
> Description of problem: 
> 
> I think this is more a question then a bug.
> 

I think so too, so let me answer it and then close this bug :)

> After doing a clean install of Fedora 13 on a system with two disks in a raid1
> configuration on a Fasttrak Tx2000 firmware/bios fake raid controller (yeah I
> know that's cheap), the file system is mounted on /dev/mapper/pdc_efihghgip1.
> 
> Is this supposed to be so?
> 
> I mean, when I look at the output of the dmevent_tool:
> 
> dmevent_tool -mu
> pdc_efihghgip2 not monitored
> pdc_efihghgip1 not monitored
> pdc_efihghgi not monitored
> 

This is really quite simple,
/dev/mapper/pdc_efihghgi

Is the entire set, just think of it as a virtual disk and just like a real disk
it has a partition table and partitions on it.

/dev/mapper/pdc_efihghgip1
is the first partition usually (*) this contains /boot and is mounted as /boot
/dev/mapper/pdc_efihghgip2
Is the second partition usually (*) this contains one big physical volume on top
of which a Volume group is build which contains logical volumes for
/, /home and swap.

*) usually means when you used auto partitioning during the installation if you did a custom install things can be very different.

Regards,

Hans

Note You need to log in before you can comment on or make changes to this bug.