Date: Fri, 28 Nov 2003 15:06:40 +0100 From: Ronald Klop <ronald-freebsd4@klop.yi.org> To: Ronald Klop <ronald-freebsd3@klop.yi.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Solved: Re: order in fstab and md/mfs (extra info) Message-ID: <oprzcphenvbhn7s1@outgoing.local> In-Reply-To: <opry373gjx87l8rq@outgoing.local> References: <opry37pvwoctc7ez@outgoing.local> <opry373gjx87l8rq@outgoing.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, I found out, that md wasn't loaded as a module and not compiled into the kernel. MD_LOAD="YES" in /boot/loader.conf fixed the problem. Ronald. On Mon, 24 Nov 2003 01:10:18 +0100, Ronald Klop <ronald-freebsd3@klop.yi.org> wrote: > On Mon, 24 Nov 2003 01:02:09 +0100, Ronald Klop > <ronald_at_echteman_dot_nl> wrote: > >> Hello, >> >> Today I noticed my mfs on /tmp not mounting properly, because of the >> order of the entries in fstab. >> Mfs can't be mounted too early. Is this meant to be or should there be >> a second stage for this mount, just like nfs mounts which are deferred >> until after the network is up. >> >> I saw it is documented in one line in 'man fstab', that order is >> important, but not many examples about this. >> >> Running 5.2-BETA cvsupped today on P-II 400Mhz (UP), 256 MB, IDE. > > It still fails with: > mfs: mdconfig (attach) exited with error code 1 > Mounting /etc/fstab filesystems failed, startup aborted > > Any hints? Same experiences? > > Ronald. -- Ronald Klop Amsterdam, The Netherlands
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprzcphenvbhn7s1>