6,534
edits
Changes
created
== Changes ==
Since {{kernel link|rhel6-testing|042stab078.6}}:
* [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)
* [nfs] NFSv4 support inside a CT has been added/corrected/enhanced, plus online migration of such CTs is supported now (PSBM-17798, PSBM-17795)
: 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.
* [sunrpc] false positive external usage report on a CT stop has been eliminated
* [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.
Since {{kernel link|rhel6-testing|042stab078.6}}:
* [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)
* [nfs] NFSv4 support inside a CT has been added/corrected/enhanced, plus online migration of such CTs is supported now (PSBM-17798, PSBM-17795)
: 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.
* [sunrpc] false positive external usage report on a CT stop has been eliminated
* [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.
