Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Apr 2012 14:59:54 -0500
From:      Adam Vande More <amvandemore@gmail.com>
To:        Matthias Apitz <guru@unixarea.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: mounting ext2fs
Message-ID:  <CA+tpaK0_N3KCS5uwfWG9E+7-e_Qz2p=Lov4uGv4i_G65jvYzeg@mail.gmail.com>
In-Reply-To: <20120419185902.GA1292@tiny>
References:  <201204181259.q3ICx2ZJ052422@fire.js.berklix.net> <4f90406e.wUY9XXMDqOEhzRDN%perryh@pluto.rain.com> <20120419123609.GA1195@tiny> <alpine.BSF.2.00.1204190828010.45169@wonkity.com> <20120419185902.GA1292@tiny>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Apr 19, 2012 at 1:59 PM, Matthias Apitz <guru@unixarea.de> wrote:

> What do you expect exactly from this command? The actual shell will open
> /dev/da0 for writing + truncating and will connect (dup) its fd 1 to it;
> then it will execute 'true', perhaps as buit-in; so what?
>

As he stated, it forces a GEOM retasting which is something necessary when
dealing with removable media.  However I don't think it will help in this
case as the device is already seen.  More likely the problem is the fs
itself.   I'm having trouble discerning the current problem you are trying
to solve given the scattered nature of the thread, but in general trouble
mounting ext2/3 fs results from one of 3 things.

GEOM doesn't see the partion which is what the "true > /dev/da0" fixes
The fs wasn't dismounted cleanly and needs to be fsck'd
The fs was created in a manner incompatible with FreeBSD ext2/3 support.

-- 
Adam Vande More



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CA+tpaK0_N3KCS5uwfWG9E+7-e_Qz2p=Lov4uGv4i_G65jvYzeg>