Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Jan 2018 07:26:11 +0000
From:      Alexey Dokuchaev <danfe@FreeBSD.org>
To:        Ed Maste <emaste@FreeBSD.org>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r327890 - head/usr.sbin/bsdinstall/partedit
Message-ID:  <20180118072611.GA51638@FreeBSD.org>
In-Reply-To: <20180113065347.GA26333@FreeBSD.org>
References:  <201801122025.w0CKPvVk022670@repo.freebsd.org> <20180113065347.GA26333@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 13, 2018 at 06:53:47AM +0000, Alexey Dokuchaev wrote:
> On Fri, Jan 12, 2018 at 08:25:57PM +0000, Ed Maste wrote:
> > New Revision: 327890
> > URL: https://svnweb.freebsd.org/changeset/base/327890
> > 
> > Log:
> >   bsdinstall: disable SUJ by default
> >   
> >   SUJ + cg checksums produce spurious warnings after an unclean shutdown
> >   (e.g. a crash).  For now disable SUJ for UFS installs so installing from
> >   a FreeBSD 12 snapshot results in a usable filesystem, until this can be
> >   fixed.
> 
> Thanks; I keep seeing it quite often.  Is it safe to disable SUJ on already
> populated filesystem?  Can (should) it better be done on live, mounted one,
> of better off the other booted instance of FreeBSD (from another media)?

Ping.

./danfe



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