forked from docs/doc-exports
zhangyue
b31ce937d8
Reviewed-by: Muller, Martin <martin.muller@t-systems.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
20 lines
3.1 KiB
HTML
20 lines
3.1 KiB
HTML
<a name="sfs_01_0082"></a><a name="sfs_01_0082"></a>
|
|
|
|
<h1 class="topictitle1">What Can I Do If Data of My File System Is Not the Same When Accessed from Two Client Servers?</h1>
|
|
<div id="body1571368802666"><div class="section" id="sfs_01_0082__section41158684111639"><h4 class="sectiontitle">Symptom</h4><p id="sfs_01_0082__p39221336111646">A file system was mounted to two servers. There was a delay in synchronizing files from one server to another. However, there was no delay when files were uploaded to a server.</p>
|
|
</div>
|
|
<div class="section" id="sfs_01_0082__section75191483415"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="sfs_01_0082__p814811102519">Add <strong id="sfs_01_0082__b11543337202210">noac, lookupcache=none</strong> to the mount command.</p>
|
|
<p id="sfs_01_0082__p8468205604119">The <strong id="sfs_01_0082__b2012744562312">noac</strong> option disables file attribute caching and forces write synchronization. By default, an NFS client's file attribute information is cached using the <strong id="sfs_01_0082__b318971910219">ac</strong> option to improve performance, and the client checks file attribute information periodically and updates it if there are any changes. Within the cache validity period, the client does not check whether file attribute information on the server is changed. By default, the value of this option is <strong id="sfs_01_0082__b1423777122318">ac</strong>. Set it to <strong id="sfs_01_0082__b12197202213232">noac</strong>.</p>
|
|
<p id="sfs_01_0082__p3857837259">The <strong id="sfs_01_0082__b11695204513254">lookupcache</strong> option is related to directory entry caching, and the value can be <strong id="sfs_01_0082__b9257012174315">all</strong>, <strong id="sfs_01_0082__b2823914154318">none</strong>, <strong id="sfs_01_0082__b6552820124315">pos</strong>, or <strong id="sfs_01_0082__b158819228433">positive</strong>. With <strong id="sfs_01_0082__b5750205944313">lookupcache=none</strong>, the client neither trust the positive nor negative lookup results. In this way, lookup caching is disabled.</p>
|
|
</div>
|
|
<div class="section" id="sfs_01_0082__section635392619212"><h4 class="sectiontitle">Solution</h4><ol id="sfs_01_0082__ol9835123119449"><li id="sfs_01_0082__li86473084518"><span>Unmount the file system if it has been mounted. To unmount a file system, see <a href="sfs_01_0026.html">Unmount a File System</a>.</span></li><li id="sfs_01_0082__li1583543134412"><span>Complete the preparations before mounting the file system. For details, see <a href="sfs_01_1001.html">Mounting an NFS File System to ECSs (Linux)</a>.</span></li><li id="sfs_01_0082__li1874943054413"><span>Mount the file system.</span><p><pre class="screen" id="sfs_01_0082__screen79405318553"><strong id="sfs_01_0082__b12946183165520">mount -t nfs -o vers=3,timeo=600,noac,lookupcache=none,noresvport,nolock</strong> <em id="sfs_01_0082__i65841642204011">Shared path</em> <em id="sfs_01_0082__i1371964974018">Local path</em></pre>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0079.html">Networks</a></div>
|
|
</div>
|
|
</div>
|
|
|