tbd Sun Microsystems, Inc.
* version 1.8.0
* Support for kernels:
- 2.6.9-67.0.4.EL (RHEL 4),
2.6.16.54-0.2.5 (SLES 10),
- 2.6.18-53.1.14.el5 (RHEL 5).
+ 2.6.18-53.1.14.el5 (RHEL 5),
+ 2.6.22.14 vanilla (kernel.org).
* Client support for unpatched kernels:
(see http://wiki.lustre.org/index.php?title=Patchless_Client)
2.6.16 - 2.6.21 vanilla (kernel.org)
* RHEL 4 and RHEL 5/SLES 10 clients behaves differently on 'cd' to a
removed cwd "./" (refer to Bugzilla 14399).
+Severity : enhancement
+Bugzilla : 15316
+Description: build kernel-ib packages for OFED 1.3 in our release cycle
+
+Severity : minor
+Bugzilla : 13969
+Frequency : always
+Description: fix SLES kernel versioning
+Details : the kernel version for our SLES 10 kernel did not include a "-"
+ before the "smp" at the end. while this was not a problem in
+ general, it did mean that software trying to use the kernel
+ version to try to detect a vendor specific kernel would fail.
+ this was most evident by the OFED build scripts.
+
+Severity : normal
+Bugzilla : 14803
+Description: Don't update lov_desc members until making sure they are valid
+Details : When updating lov_desc members via proc fs, need fix their
+ validities before doing the real update.
+
+Severity : normal
+Bugzilla : 15069
+Description: don't put request into delay list while invalidate in flight.
+Details : ptlrpc_delay_request sometimes put in delay list while invalidate
+ import in flight. this produce timeout for invalidate and sometimes
+ can cause stale data.
+
+Severity : minor
+Bugzilla : 14856
+Frequency : on ppc only
+Description: not convert ost objects for directory because it's not exist.
+Details : ll_dir_getstripe assume dirrectory has ost objects but this wrong.
+
+Severity : normal
+Bugzilla : 12652
+Description: Add FMODE_EXEC file flag for SLES10 SP1 kernel.
+
+Severity : enhancement
+Bugzilla : 13397
+Description: Update to support 2.6.22.14 vanilla kernel.
+
Severity : normal
Bugzilla : 14533
Frequency : rare, on recovery
Description: read procfs can produce deadlock in some situation
Details : Holding lprocfs lock which send rpc can produce block for destroy
- obd objects and this also block reconnect with -EALREADY. This isn't
- fix all lprocfs bugs - but make it rare.
+ obd objects and this also block reconnect with -EALREADY. This isn't
+ fix all lprocfs bugs - but make it rare.
Severity : enhancement
Bugzilla : 15152
Bugzilla : 14321
Description: lustre_mgs: operation 101 on unconnected MGS
Details : When MGC is disconnected from MGS long enough, MGS will evict the
- MGC, and late on MGC cannot successfully connect to MGS and a lot
+ MGC, and late on MGC cannot successfully connect to MGS and a lot
of the error messages complaining that MGS is not connected.
Severity : major
Details : void sending multiple quota reqs to mds, which will keep the
status between the reqs.
-Severity : normal
+Severity : normal
Bugzilla : 13125
Description: osts not allocated evenly to files
-Details : change the condition to increase offset_idx
+Details : change the condition to increase offset_idx
Severity : critical
Frequency : Always for filesystems larger than 2TB on 32-bit systems.
Bugzilla : 14379
Description: Properly match for duplicate locks
Details : Due to different lock order from skiplists code, we need to
- traverse entire list for now
+ traverse entire list for now
+
+Severity : normal
+Frequency : only on PPC/SLES10
+Bugzilla : 14855
+Description: "BITS_PER_LONG is not 32 or 64" in linux/idr.h
+Details : On SLES10/PPC, fs.h includes idr.h which requires BITS_PER_LONG to
+ be defined. Add a hack in mkfs_lustre.c to work around this compile
+ issue.
+
+Severity : normal
+Bugzilla : 14257
+Description: LASSERT on MDS when client holding flock lock dies
+Details : ldlm pool logic depends on number of granted locks equal to
+ number of released locks which is not true for flock locks, so
+ just exclude such locks from consideration.
+
+Severity : normal
+Bugzilla : 15188
+Description: MDS deadlock with many ll_sync_lov threads and I/O stalled
+Details : Use fsfilt_sync() for both the whole filesystem sync and
+ individual file sync to eliminate dangerous inode locking
+ with I_LOCK that can lead to a deadlock.
+
+Severity : normal
+Bugzilla : 14410
+Description: performance in 1.6.3
+Details : Force q->max_phys_segments to MAX_PHYS_SEGMENTS on SLES10 to be
+ sure that 1MB requests are not fragmented by the block layer.
--------------------------------------------------------------------------------
git://git.whamcloud.com / fs / lustre-release.git / blobdiff