Re: A few CURRENT problems

On Fri, Jan 07, 2005 at 02:36:31PM +0100, Erik Trulsson wrote:
> 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.)

A quick check in the kernel source reveals the following code snippet
(from src/sys/ufs/ffs/ffs_vfsops.c  - identical code is in both
RELENG_4 and RELENG_5)

                /*
                 * 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 (mp->mnt_flag & MNT_SOFTDEP)
                        mp->mnt_flag &= ~MNT_ASYNC;
 

Which confirms that is softupdates is enabled for a filesystem (as you
seem to have according to the output of mount quoted above) then
"async" will be disabled for that filesystem.


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013_at_student.uu.se