Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Jan 2005 14:36:31 +0100
From:      Erik Trulsson <ertr1013@student.uu.se>
To:        Daniel Eriksson <daniel_k_eriksson@telia.com>
Cc:        =?iso-8859-1?Q?'S=F8ren?= Schmidt' <sos@DeepCore.dk>
Subject:   Re: A few CURRENT problems
Message-ID:  <20050107133631.GA47934@falcon.midgard.homeip.net>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAFq8e/92cLk6Q1zpeIhImOAEAAAAA@telia.com>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAFq8e/92cLk6Q1zpeIhImOAEAAAAA@telia.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, Jan 07, 2005 at 12:25:16PM +0100, Daniel Eriksson wrote:
> 
> Here are four issues I currently have with CURRENT:
> 
> * Mounting a filesystem async no longer seems to work. After mounting a
> filesystem like this: "mount -o noatime,async /dev/da1s1d
> /some/mount/point", mount does not report the filesystem as being mounted
> async: "/dev/da1s1d on /some/mount/point (ufs, local, noatime,
> soft-updates)"
> I have not had time to verify if the filesystem is actually mounted async or
> not, or if it is just a missing attribute output in the list produced by
> "mount". I don't know exactly when this stopped "working", but the newmount
> commit is my prime suspect. I do remember seeing "async" listed as a
> filesystem attribute ~2 months ago.

Disable softupdates for that filesystem. If you have softupdates
enabled for a filesystem this seems to override async/sync.
(This applies not only to -CURRENT but to 5-STABLE and 4-STABLE as
well.)



-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20050107133631.GA47934>