First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 171593
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: udev maintainers <udev-bugs@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matthias Schwarzott <zzam@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 171593 depends on: Show dependency tree
Show dependency graph
Bug 171593 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)









View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-03-20 17:42 0000
The rcscript addon udev-start.sh calls volume-managers to create its device
nodes for already active volumes. This is only needed for the checkroot
init-script, as / is already mounted, and after checkroot the normal addons for
volume-managers are started.

To not get more problems with volume-orders (not being configurable at that
place) we should remove that part completely, see Bug #170027.

Only remaining problem to be solved then, is: 
checkroot init-script, which calls "fsck /".
fsck then tries to access device-node for root device (getting the info from
fstab/its internal db).

Uberlord suggested to just disable fs-checking in fstab for cases where
/dev/mapper/.... (which is garanteed to exist) cannot be easily used in fstab.

------- Comment #1 From SpanKY 2007-03-22 07:27:19 0000 -------
i dont think i got back to you on this after we chatted about it in the base
channel ...

for baselayout-1.12.x, we'll happily move the volume crap into the checkfs
script

for 1.13.x and beyond, we'll move to proper init.d scripts

------- Comment #2 From Matthias Schwarzott 2007-05-05 07:37:57 0000 -------
The problem is now reduced to baselayout-1.
udev-start.sh no longer executes this code for baselayout-2.

------- Comment #3 From Matthias Schwarzott 2007-10-10 13:09:37 0000 -------
@robbat, Cardoe:
I found some code, that basically is/was the Phase I of volume-init we talked
about yesterday.

This code is from udev-start-104-r12.sh:
        # Create nodes that udev can't
        ebegin "Finalizing udev configuration"
        [ -x /sbin/dmsetup ] && /sbin/dmsetup mknodes &>/dev/null
        [ -x /sbin/lvm ] && \
                /sbin/lvm vgscan -P --mknodes --ignorelockingfailure
&>/dev/null
        # Running evms_activate on a LiveCD causes lots of headaches
        [ -z "${CDBOOT}" ] && [ -x /sbin/evms_activate ] && \
                /sbin/evms_activate -q &>/dev/null
        eend 0


It got reduced for newer udev versions to (from udev-start-115-r6.sh):

        # Only do this for baselayout-1*
        if [ ! -e /lib/librc.so ]; then

                # Create nodes that udev can't
                ebegin "Finalizing udev configuration"
                [ -x /sbin/lvm ] && \
                        /sbin/lvm vgscan -P --mknodes --ignorelockingfailure
&>/dev/null
                # Running evms_activate on a LiveCD causes lots of headaches
                [ -z "${CDBOOT}" -a -x /sbin/evms_activate ] && \
                        /sbin/evms_activate -q &>/dev/null
                eend 0
        fi

------- Comment #4 From Robin Johnson 2007-10-10 20:49:18 0000 -------
zzam: yeah, make that code run always, and we should be good for the PhaseI.

First Last Prev Next    No search results available      Search page      Enter new bug