summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-February/012314.html
blob: f6fc6280b3818539d9b23118699c3dd7c7f73cab (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] New dracut - please test
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20dracut%20-%20please%20test&In-Reply-To=%3C4F48BF1B.4050605%40colin.guthr.ie%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="012308.html">
   <LINK REL="Next"  HREF="012341.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] New dracut - please test</H1>
    <B>Colin Guthrie</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20dracut%20-%20please%20test&In-Reply-To=%3C4F48BF1B.4050605%40colin.guthr.ie%3E"
       TITLE="[Mageia-dev] New dracut - please test">mageia at colin.guthr.ie
       </A><BR>
    <I>Sat Feb 25 11:59:39 CET 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="012308.html">[Mageia-dev] New dracut - please test
</A></li>
        <LI>Next message: <A HREF="012341.html">[Mageia-dev] New dracut - please test
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#12314">[ date ]</a>
              <a href="thread.html#12314">[ thread ]</a>
              <a href="subject.html#12314">[ subject ]</a>
              <a href="author.html#12314">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>'Twas brillig, and David W. Hodgins at 25/02/12 07:35 did gyre and gimble:
&gt;<i> On Fri, 24 Feb 2012 06:42:01 -0500, Colin Guthrie
</I>&gt;<i> &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt; wrote:
</I>&gt;<i> 
</I>&gt;&gt;<i> The other big change here is to automatically generate a much bigger
</I>&gt;&gt;<i> initramfs when doing an upgrade from mga1. This will include a lot more
</I>&gt;&gt;<i> stuff (e.g. lvm, raid etc) that may or may not be needed on a given
</I>&gt;&gt;<i> setup, but until you boot with dracut you cannot generate an initramfs
</I>&gt;&gt;<i> that will be able to detect only what is needed for boot.
</I>&gt;<i> 
</I>&gt;<i> Looking at the current version of the init script, it's clear
</I>&gt;<i> what the problem is ...
</I>&gt;<i> 
</I>&gt;<i>     check_finished &amp;&amp; break
</I>&gt;<i> 
</I>&gt;<i>     udevsettle
</I>&gt;<i> 
</I>&gt;<i>     check_finished &amp;&amp; break
</I>&gt;<i> 
</I>&gt;<i> The above statement will always be true on a single core
</I>&gt;<i> system, so the following code never gets executed.
</I>
As I've said before, I really do not think this is anything to do with
number of cores. I do see that there is a chicken and egg problem, but
why would the number of cores affect this? Nothing runs in the
background here.

As stated earlier
(<A HREF="https://www.mageia.org/pipermail/mageia-dev/2012-February/011709.html">https://www.mageia.org/pipermail/mageia-dev/2012-February/011709.html</A>),
the problem is simply that there are no calls to wait_for_dev for the
lvm drives and thus the whole initqueue stuff just glosses over things
and doesn't ever activate them.

What is different to the last time is that now for hostonly initrds (not
the one you generated), the wait_for_dev call WILL be added. I had hoped
this different approach would have fixed your problem.

However, due to me now doing this fallback non-hostonly initrd, the
original problem still manifests itself.

Can you test that generating a new initrd after booting via dracut (and
thus getting a hostonly one) does actually activate your usr partition?
I'm not 100% convinced there will not still be a problem with the
&quot;resume&quot; support and swap partitions, but it will hopefully give you a
smooth boot even if resume support is busted.

The non-hostonly problem does need a fix and I'll see what can be done.

Col




-- 

Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>

Day Job:
  Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
  Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
  PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
  Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>























<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="012308.html">[Mageia-dev] New dracut - please test
</A></li>
	<LI>Next message: <A HREF="012341.html">[Mageia-dev] New dracut - please test
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#12314">[ date ]</a>
              <a href="thread.html#12314">[ thread ]</a>
              <a href="subject.html#12314">[ subject ]</a>
              <a href="author.html#12314">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>