* CONFIGURATION CHANGE. This version of Lustre WILL NOT
INTEROPERATE with older versions automatically. In many cases a
special upgrade step is needed. Please read the
- user documentation before upgrading any part of a live system.
- * WIRE PROTOCOL CHANGE from previous 1.6 beta versions. This
- version will not interoperate with 1.6 betas before beta7 (1.5.97).
+ user documentation before upgrading any part of a 1.4.x system.
* WARNING: Lustre configuration and startup changes are required with
this release. See https://mail.clusterfs.com/wikis/lustre/MountConf
for details.
+ * Support for kernels:
+ 2.6.9-42.0.3EL (RHEL 4)
+ 2.6.5-7.276 (SLES 9)
+ 2.4.21-47.0.1.EL (RHEL 3)
+ 2.6.12.6 vanilla (kernel.org)
+ 2.6.16.21-0.8 (SLES10)
+ * Client support for unpatched kernels:
+ (see https://mail.clusterfs.com/wikis/lustre/PatchlessClient)
+ 2.6.16 - 2.6.19 vanilla (kernel.org)
+ 2.6.9-42.0.3EL (RHEL 4)
* Recommended e2fsprogs version: 1.39.cfs2-0
* bug fixes
+Severity : major
+Frequency : liblustre (e.g. catamount) on a large cluster with >= 8 OSTs
+ per OSS
+Bugzilla : 11684
+Description: System hang on startup
+Details : This bug allowed the liblustre (e.g. catamount) client to
+ return to the app before handling all startup RPCs. This
+ could leave the node unresponsive to lustre network traffic
+ and manifested as a server ptllnd timeout.
+
+Severity : enhancement
+Bugzilla : 11667
+Description: Add "/proc/sys/lustre/debug_peer_on_timeout"
+ (liblustre envirable: LIBLUSTRE_DEBUG_PEER_ON_TIMEOUT)
+ boolean to control whether to print peer debug info when a
+ client's RPC times out.
+
Severity : enhancement
Bugzilla : 8007
Description: MountConf
and bits policy, thus improving the performance of search through
the granted list.
+Severity : major
+Frequency : only if OST filesystem is corrupted
+Bugzilla : 9829
+Description: client incorrectly hits assertion in ptlrpc_replay_req()
+Details : for a short time RPCs with bulk IO are in the replay list,
+ but replay of bulk IOs is unimplemented. If the OST filesystem
+ is corrupted due to disk cache incoherency and then replay is
+ started it is possible to trip an assertion. Avoid putting
+ committed RPCs into the replay list at all to avoid this issue.
+
+Severity : minor
+Frequency : only for kernels with patches from Lustre below 1.4.3
+Bugzilla : 11248
+Description: Remove old rdonly API
+Details : Remove old rdonly API which unsed from at least lustre 1.4.3
+
------------------------------------------------------------------------------
TBD Cluster File Systems, Inc. <info@clusterfs.com>
Description: Crash on NFS re-export node
Details : under very unusual load conditions an assertion is hit in
ll_intent_file_open()
-
+
+Severity : normal
+Frequency : always
+Bugzilla : 10901
+Description: large O_DIRECT requests fail under memory pressure/fragmentation
+Details : Large single O_DIRECT read and write calls can fail to allocate
+ a sufficiently large buffer to process the request. In case of
+ allocation failure the allocation is retried with a smaller
+ buffer and broken into smaller requests.
+
+Severity : normal
+Frequency : always
+Bugzilla : 3244
+Description: Addition of EXT3_FEATURE_RO_COMPAT_DIR_NLINKS flag for
+ > 32000 subdirectories
+Details : Add EXT3_FEATURE_RO_COMPAT_DIR_NLINK flag to
+ EXT3_FEATURE_RO_COMPAT_SUPP. This flag will be set whenever
+ subdirectory count crosses 32000. This will aid e2fsck to
+ correctly handle more than 32000 subdirectories.
+
------------------------------------------------------------------------------
TBD Cluster File Systems, Inc. <info@clusterfs.com>
git://git.whamcloud.com / fs / lustre-release.git / blobdiff