Date: Fri, 19 Aug 2011 18:54:26 +0000 From: Alexander Best <arundel@freebsd.org> To: Kirk McKusick <mckusick@mckusick.com> Cc: freebsd-fs@freebsd.org Subject: Re: probably embarrassing SUJ question Message-ID: <20110819185426.GA77630@freebsd.org> In-Reply-To: <201108191752.p7JHqHEt030978@chez.mckusick.com> References: <20110819174033.GA68015@freebsd.org> <201108191752.p7JHqHEt030978@chez.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri Aug 19 11, Kirk McKusick wrote:
> > Date: Fri, 19 Aug 2011 17:40:33 +0000
> > From: Alexander Best <arundel@freebsd.org>
> > To: freebsd-fs@freebsd.org
> > Subject: probably embarrassing SUJ question
> >
> > Hi there,
> >
> > I recently saw somebody using mount -o async in combination with
> > gjournal. I just wanted to ask, whether async can also be used with
> > SUJ? or will this put me in a dangerous situation, where my fs will
> > get hosed after a crash?
> >
> > cheers.
> > alex
>
> The async flag is incompatible with soft updates or journaled
> soft updates. But not to fear, we added a seatbelt in ffs_mount:
>
> /*
> * Soft updates is incompatible with "async",
> * so if we are doing softupdates stop the user
> * from setting the async flag in an update.
> * Softdep_mount() clears it in an initial mount
> * or ro->rw remount.
> */
> if (MOUNTEDSOFTDEP(mp)) {
> MNT_ILOCK(mp);
> mp->mnt_flag &= ~MNT_ASYNC;
> MNT_IUNLOCK(mp);
> }
>
> So, nothing bad will happen.
ah..thanks a lot. good thing you provide such kind of seatbelts. :)
cheers.
alex
>
> Kirk McKusick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110819185426.GA77630>