Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Jan 2009 11:47:57 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        obrien@freebsd.org
Cc:        bsam@ipt.ru, freebsd-current@freebsd.org, fbsdlist@src.cx
Subject:   Re: gjournal is not automounted any more
Message-ID:  <20090102.114757.-924277930.imp@bsdimp.com>
In-Reply-To: <20090102091334.GA41230@dragon.NUXI.org>
References:  <ed91d4a80812310908ndc0afeeqa277c7a718ab429f@mail.gmail.com> <69321574@bs1.sp34.ru> <20090102091334.GA41230@dragon.NUXI.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20090102091334.GA41230@dragon.NUXI.org>
            "David O'Brien" <obrien@freebsd.org> writes:
: On Wed, Dec 31, 2008 at 10:45:13PM +0300, Boris Samorodov wrote:
: > "Artem Belevich" <fbsdlist@src.cx> writes:
: > 
: > >> /dev/mirror/gm0.journal /m              ufs,async  rw           2       2
: > >
: > > Looks like there's an error in your fstab. You've added "async" to the
: > > filesystem type instead of mount options. It should probably look like
: > > this:
: > >
: > > /dev/mirror/gm0.journal /m              ufs      async,rw           2       2
: > >
: > > Might explain why mount does not like it.
: > 
: > Hm, well... You are right. But it used to work so far though...
: 
: Before 'fsck' would read the lable for the FS type.  That has changed and
: thus you cannot just 'fsck /dev/ad1s1d' anymore.  So the FS type in fstab
: must be accurate.

Why did that change?  I routinely have disks that aren't in my
/etc/fstab that I mount and this is a pain in the backside.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090102.114757.-924277930.imp>