From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Heflin, Roger A." <Roger.A.Heflin@conocophillips.com>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: NFS mount option - noac forces sync even if async is specified, and no warning is given
Date: 03 Feb 2003 21:49:56 +0100 [thread overview]
Message-ID: <shsr8ap5bt7.fsf@charged.uio.no> (raw)
In-Reply-To: <5CA6F03EF05E0046AC5594562398B916A7F982@POEXMB3.conoco.net>
>>>>> " " == Roger A Heflin <Heflin> writes:
> I run the following command:
> mount -t nfs -o rw,hard,lock,intr,noac,async
> hoepld31:/ptmp/hoepld31 /tmpmnt/ptmp/hoepld31
> And then cat /proc/mounts:
> hoepld31:/ptmp/hoepld31 /tmpmnt/ptmp/hoepld31 nfs
> rw,sync,v3,rsize=8192,
> wsize=8192,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,intr,
> udp,noac,lock,addr=hoepld31 0 0
> Note that async is specified on the mount line and /proc/mounts
> specifies that sync was used. If I don't use the async option
That's right. 'noac' enforces 'sync' in order to remain compatible
with the expected behaviour of noac on other NFS client
implementations.
If you don't need 'sync', you can specify
acregmin=0,acregmax=0,acdirmin=0,acdirmax=0
instead.
Cheers,
Trond
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-03 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 18:28 NFS mount option - noac forces sync even if async is specified, and no warning is given Heflin, Roger A.
2003-02-03 20:49 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 16:04 Heflin, Roger A.
2003-02-05 21:50 Heflin, Roger A.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shsr8ap5bt7.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Roger.A.Heflin@conocophillips.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox