We are pleased to announce that the Lustre 2.4.1 Release has been declared GA and is
available for
download<http://downloads.whamcloud.com/public/lustre/latest-maintenan... .
You can also grab the source from
git<http://git.whamcloud.com/?p=fs/lustre-release.git;a=commit;h=cdc7c...
The release highlights are
LU-3415<https://jira.hpdd.intel.com/browse/LU-3415>: It is now possible to upgrade
from 1.8.x to 2.4.0 with quotas enabled without hitting an LBUG
<
https://jira.hpdd.intel.com/browse/LU-3420>L<https://jira.hpdd.inte...;:
OI scrub will now be engaged after a file level backup running with DNE
<
https://jira.hpdd.intel.com/browse/LU-3421>L<https://jira.hpdd.inte...;:
A case where OSTs might erroneously report ENOSPC has been identified and fixed
L<https://jira.hpdd.intel.com/browse/LU-3305>U-3305<https://jira...;:
A metadata performance drop running with quotas enabled has been addressed
Fuller details can be found in the change
log<https://wiki.hpdd.intel.com/display/PUB/Changelog+2.4>
The following are known issues in the Lustre 2.4.1 Release:
LU-3027<https://jira.hpdd.intel.com/browse/LU-3027>: A race condition can result in
mis-reporting of file size
LU-3430<https://jira.hpdd.intel.com/browse/LU-3430> : A rare race can result in an
LBUG on an OSS while running the orr policy for NRS
LU-3544<https://jira.hpdd.intel.com/browse/LU-3544>: Re-exporting Lustre over NFS
from SLES11 SP2 has known issues
LU-3934<https://jira.hpdd.intel.com/browse/LU-3934>: Files created under Lustre
1.8.x could be inaccessible for a filesystem first upgraded to 2.1.x and then subsequently
upgraded to 2.4.1 with a client remaining mounted. The workaround it to manually trigger
an OI scrub after the upgrade.
Work is in progress for these issues.
Please log any issues found in the issue tracking
system<https://jira.hpdd.intel.com/>