Mounting root...
Pawel Jakub Dawidek
pjd at FreeBSD.org
Mon Aug 23 13:52:46 PDT 2004
On Mon, Aug 23, 2004 at 01:44:58PM -0700, Brooks Davis wrote:
+> On Mon, Aug 23, 2004 at 10:38:55PM +0200, Pawel Jakub Dawidek wrote:
+> > On Mon, Aug 23, 2004 at 03:01:57PM -0500, Dan Nelson wrote:
+> > +> How about maybe blocking on the initial access to a degraded mirror for
+> > +> 5 (just a guess) seconds to see if the other half shows up? If it
+> > +> doesn't, assume it's never showing up and use what you have. When the
+> > +> other disk arrives, sync your changes over to it. [...]
+> >
+> > I'm waiting for few seconds for the rest of components now, but mounting
+> > root routine doesn't wait for me.
+> > And I'm not going to create provider without given a chance to the rest
+> > components to show up, because I can end up with mirror started on stale
+> > component, because a fresh one showed up with some delay.
+>
+> Would it be feasiable to create the provider immediatly and journal
+> writes up to a certain period of time/data size before degrading the
+> array?
Everything is possible, but I just want to suggest, that we have more and
more GEOM classes and we should rethink our boot process, because raw disks
aren't the only providers used in mount process and not all providers have
to show up immediatelly. The best solution will be probably to ask every
class if it waits for something or not.
--
Pawel Jakub Dawidek http://www.FreeBSD.org
pjd at FreeBSD.org http://garage.freebsd.pl
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20040823/b39e6442/attachment.bin
More information about the freebsd-arch
mailing list