tbd Sun Microsystems, Inc.
* version 2.0.0
* Support for kernels:
- 2.6.16.60-0.27 (SLES 10),
+ 2.6.16.60-0.31 (SLES 10),
2.6.18-92.1.10.el5 (RHEL 5),
2.6.22.14 vanilla (kernel.org).
* Client support for unpatched kernels:
* RHEL 4 and RHEL 5/SLES 10 clients behaves differently on 'cd' to a
removed cwd "./" (refer to Bugzilla 14399).
* File join has been disabled in this release, refer to Bugzilla 16929.
+
+Severity : enhancement
+Bugzilla : 17458
+Description: Update to SLES10 SP2 kernel-2.6.16.60-0.31.
+
+Severity : enhancement
+Bugzilla : 14166
+Description: New client IO stack (CLIO).
+
+Severity : enhancement
+Bugzilla : 15393
+Description: Commit on sharing. Eliminate inter-client dependencies between
+ uncommitted transactions by doing transaction commits.
+ Thereby clients may recovery independently.
+
+Severity : normal
+Frequency : Create a symlink file with a very long name
+Bugzilla : 16578
+Description: ldlm_cancel_pack()) ASSERTION(max >= dlm->lock_count + count)
+Details : If there is no extra space in the request for early cancels,
+ ldlm_req_handles_avail() returns 0 instead of a negative value.
Severity : enhancement
Bugzilla : 1819
Severity : normal
Bugzilla : 16450
Description: Add lu_ref support to ldlm_lock
-Details : lu_ref support for ldlm_lock and ldlm_resource. See lu_ref patch.
- lu_ref fields ->l_reference and ->lr_reference are added to ldlm_lock
- and ldlm_resource. LDLM interface has to be changed, because code that
+Details : lu_ref support for ldlm_lock and ldlm_resource. See lu_ref patch.
+ lu_ref fields ->l_reference and ->lr_reference are added to ldlm_lock
+ and ldlm_resource. LDLM interface has to be changed, because code that
releases a reference on a lock, has to "know" what reference this is.
In the most frequent case
...
LDLM_LOCK_PUT(lock);
- no changes are required. When any other reference (received _not_ from
- ldlm_handle2lock()) is released, LDLM_LOCK_RELEASE() has to be called
+ no changes are required. When any other reference (received _not_ from
+ ldlm_handle2lock()) is released, LDLM_LOCK_RELEASE() has to be called
instead of LDLM_LOCK_PUT().
Arguably, changes are pervasive, and interface requires some discipline
- for proper use. On the other hand, it was very instrumental in finding
+ for proper use. On the other hand, it was very instrumental in finding
a few leaked lock references.
Severity : normal
Severity : normal
Bugzilla : 16450
Description: Add ldlm_weigh_callback().
-Details : Add new ->l_weigh_ast() call-back to ldlm_lock. It is called
+Details : Add new ->l_weigh_ast() call-back to ldlm_lock. It is called
by ldlm_cancel_shrink_policy() to estimate lock "value", instead of
hard-coded `number of pages' logic.
Severity : normal
Bugzilla : 16450
Description: Add start and stop methods to lu_device_type_operations.
-Details : Introduce two new methods in lu_device_type_operations, that are
- invoked when first instance of a given type is created and last one
+Details : Introduce two new methods in lu_device_type_operations, that are
+ invoked when first instance of a given type is created and last one
is destroyed respectively. This is need by CLIO.
Severity : normal
Bugzilla : 16450
Description: Introduce struct md_site and move meta-data specific parts of
struct lu_site here.
-Details : Move md-specific fields out of struct lu_site into special struct
+Details : Move md-specific fields out of struct lu_site into special struct
md_site, so that lu_site can be used on a client.
Severity : minor
Details : Add support for tunable preallocation window and new tunables for
large/small requests
+Severity : normal
+Bugzilla : 16680
+Description: Detect corruption of block bitmap and checking for preallocations
+Details : Checks validity of on-disk block bitmap. Also it does better
+ checking of number of applied preallocations. When corruption is
+ found, it turns filesystem readonly to prevent further corruptions.
+
+Severity : normal
+Bugzilla : 17197
+Description: (rw.c:1323:ll_read_ahead_pages()) ASSERTION(page_idx > ria->ria_stoff) failed
+Details : Once the unmatched stride IO mode is detected, shrink the stride-ahead
+ window to 0. If it does hit cache miss, and read-pattern is still
+ stride-io mode, does not reset the stride window, but also does not
+ increase the stride window length in this case.
+
+Severity : normal
+Bugzilla : 16438
+Frequency : only for big-endian servers
+Description: Check if system is big-endian while mounting fs with extents feature
+Details : Mounting a filesystem with extents feature will fail on big-endian
+ systems since ext3-based ldiskfs is not supported on big-endian
+ systems. This can be over-riden with "bigendian_extents" mount option.
+
--------------------------------------------------------------------------------
2007-08-10 Cluster File Systems, Inc. <info@clusterfs.com>
git://git.whamcloud.com / fs / lustre-release.git / blobdiff