https://wiki.openvz.org/index.php?action=history&feed=atom&title=Download%2Fkernel%2Frhel6-testing%2F042stab078.7%2FchangesDownload/kernel/rhel6-testing/042stab078.7/changes - Revision history2026-06-14T02:34:59ZRevision history for this page on the wikiMediaWiki 1.31.1https://wiki.openvz.org/index.php?title=Download/kernel/rhel6-testing/042stab078.7/changes&diff=13695&oldid=prevKir: reword nfs4 in ct2013-04-28T16:11:05Z<p>reword nfs4 in ct</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 16:11, 28 April 2013</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l3" >Line 3:</td>
<td colspan="2" class="diff-lineno">Line 3:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [fs] fsync should not change data on a frozen fs, this results in a warning "WARNING: at fs/ext4/super.c:248 ext4_journal_start_sb" and possibly - data corruption (PSBM-19460)</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [fs] fsync should not change data on a frozen fs, this results in a warning "WARNING: at fs/ext4/super.c:248 ext4_journal_start_sb" and possibly - data corruption (PSBM-19460)</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [nfs] NFSv4 support inside a CT has been added/corrected/enhanced, plus online migration of such CTs is supported now (PSBM-17798, PSBM-17795)</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [nfs] NFSv4 support inside a CT has been added/corrected/enhanced, plus online migration of such CTs is supported now (PSBM-17798, PSBM-17795)</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: NOTE: <del class="diffchange diffchange-inline">we are not going to enable </del>NFSv4 <del class="diffchange diffchange-inline">support </del>inside <del class="diffchange diffchange-inline">a </del>CT by default <del class="diffchange diffchange-inline">at least until we get a positive feedback from real customers on NFSv4 support. In order to use NFSv4 inside a CT</del>, <del class="diffchange diffchange-inline">one needs to enable </del>sysctl <del class="diffchange diffchange-inline">"nfs4_ct_enable" first </del>on the HN.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: NOTE: NFSv4 inside CT <ins class="diffchange diffchange-inline">is currently disabled </ins>by default, <ins class="diffchange diffchange-inline">can be enabled via <code>nfs4_ct_enable</code> </ins>sysctl on the HN.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [sunrpc] false positive external usage report on a CT stop has been eliminated</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [sunrpc] false positive external usage report on a CT stop has been eliminated</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [cpt/nfs] unlinked/silly-renamed files handling has been corrected. We do not look for dentry aliases anymore, we just resurrect the file and unlink it once more after the migration.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [cpt/nfs] unlinked/silly-renamed files handling has been corrected. We do not look for dentry aliases anymore, we just resurrect the file and unlink it once more after the migration.</div></td></tr>
</table>Kirhttps://wiki.openvz.org/index.php?title=Download/kernel/rhel6-testing/042stab078.7/changes&diff=13682&oldid=prevKir: created2013-04-26T20:24:01Z<p>created</p>
<p><b>New page</b></p><div>== Changes ==<br />
Since {{kernel link|rhel6-testing|042stab078.6}}:<br />
* [fs] fsync should not change data on a frozen fs, this results in a warning "WARNING: at fs/ext4/super.c:248 ext4_journal_start_sb" and possibly - data corruption (PSBM-19460)<br />
* [nfs] NFSv4 support inside a CT has been added/corrected/enhanced, plus online migration of such CTs is supported now (PSBM-17798, PSBM-17795)<br />
: NOTE: we are not going to enable NFSv4 support inside a CT by default at least until we get a positive feedback from real customers on NFSv4 support. In order to use NFSv4 inside a CT, one needs to enable sysctl "nfs4_ct_enable" first on the HN.<br />
* [sunrpc] false positive external usage report on a CT stop has been eliminated<br />
* [cpt/nfs] unlinked/silly-renamed files handling has been corrected. We do not look for dentry aliases anymore, we just resurrect the file and unlink it once more after the migration.</div>Kir