tbd Sun Microsystems, Inc.
* version 2.0.0
* Support for kernels:
- 2.6.16.54-0.2.5 (SLES 10),
- 2.6.18-53.1.21.el5 (RHEL 5),
+ 2.6.16.60-0.27 (SLES 10),
+ 2.6.18-92.1.10.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)
* RHEL 4 and RHEL 5/SLES 10 clients behaves differently on 'cd' to a
removed cwd "./" (refer to Bugzilla 14399).
+Severity : enhancement
+Bugzilla : 16633
+Description: Update to RHEL5 kernel-2.6.18-92.1.10.el5.
+
+Severity : enhancement
+Bugzilla : 16547
+Description: Update to SLES10 SP2 kernel-2.6.16.60-0.27.
+
+Severity : enhancement
+Bugzilla : 16566
+Description: Upcall on Lustre log has been dumped
+Details : Allow for a user mode script to be called once a Lustre log has
+ been dumped. It passes the filename of the dumped log to the
+ script, the location of the script can be specified via
+ /proc/sys/lnet/debug_log_upcall.
+
+Severity : minor
+Bugzilla : 16583
+Frequency : rare
+Description: avoid messages about idr_remove called for id which is not allocated.
+Details : Move assigment s_dev for clustered nfs to end of initialization, for
+ avoid problem with error handling.
+
+Severity : minor
+Bugzilla : 16109
+Frequency : rare
+Description: avoid Already found the key in hash [CONN_UNUSED_HASH] messages
+Details : When connection is reused this not moved from CONN_UNUSED_HASH into
+ CONN_USED_HASH and this prodice warning when put connection again
+ in unused hash.
+
+Severity : enhancement
+Bugzilla : 16573
+Description: Export bytes_read/bytes_write count on OSC/OST.
+
+Severity : normal
+Bugzilla : 16237
+Description: Early reply size mismatch, MGC loses connection
+Details : Apply the MGS_CONNECT_SUPPORTED mask at reconnect time so
+ the connect flags are properly negotiated.
+
+Severity : normal
+Bugzilla : 16006
+Description: Properly propagate oinfo flags from lov to osc for statfs
+Details : restore missing copy oi_flags to lov requests.
+
+Severity : enhancement
+Bugzilla : 16581
+Description: Add man pages for llobdstat(8), llstat(8), plot-llstat(8),
+ : l_getgroups(8), lst(8), routerstat(8)
+Details : included man pages for llobdstat(8), llstat(8),
+ : plot-llstat(8), l_getgroups(8), lst(8), routerstat(8)
+
+Severity : enhancement
+Bugzilla : 16091
+Description: configure's --enable-quota should check the
+ : kernel .config for CONFIG_QUOTA
+Details : configure is terminated if --enable-quota is passed but
+ : no quota support is in kernel
+
+Severity : normal
+Bugzilla : 13139
+Description: Remove portals compatibility
+Details : Remove portals compatibility, not interoperable with releases
+ before 1.4.6
+
+Severity : normal
+Bugzilla : 15576
+Description: Resolve device initialization race
+Details : Prevent proc handler from accessing devices added to the
+ obd_devs array but yet be intialized.
+
+Severity : enhancement
+Bugzilla : 15308
+Description: Update to SLES10 SP2 kernel-2.6.16.60-0.23.
+
+Severity : enhancement
+Bugzilla : 16190
+Description: Update to RHEL5 kernel-2.6.18-92.1.6.el5.
+
Severity : normal
Bugzilla : 12975
Frequency : rare
Description: Using wrong pointer in osc_brw_prep_request
Details : Access to array[-1] can produce panic if kernel compiled with
- CONFIG_PAGE_ALLOC enabled
+ CONFIG_PAGE_ALLOC enabled
Severity : normal
Bugzilla : 16037
Bugzilla : 15625
Description: *optional* service tags registration
Details : if the "service tags" package is installed on a Lustre node
- When the filesystem is mounted, a local-node service tag will
+ When the filesystem is mounted, a local-node service tag will
be created. See http://inventory.sun.com/ for more information
about the Service Tags asset management system.
Bugzilla : 15825
Description: Kernel BUG tries to release flock
Details : Lustre does not destroy flock lock before last reference goes
- away. So always drop flock locks when client is evicted and
+ away. So always drop flock locks when client is evicted and
perform unlock regardless of successfulness of speaking to MDS.
Severity : normal
Description: Oops in read and write path when failing to allocate lock.
Details : Check if lock allocation failed and return error back.
-Severity : normal
+Severity : normal
Bugzilla : 11679
Description: lstripe command fails for valid OST index
Details : The stripe offset is compared to lov->desc.ld_tgt_count
Bugzilla : 13570
Description: To avoid grant space > avaible space when the disk is almost
full. Without this patch you might see the error "grant XXXX >
- available" or some LBUG about grant, when the disk is almost
+ available" or some LBUG about grant, when the disk is almost
full.
Details : In filter_check_grant, for non_grant cache write, we should
check the left space by if (*left > ungranted + bytes), instead
- of (*left > ungranted), because only we are sure the left space
+ of (*left > ungranted), because only we are sure the left space
is enough for another "bytes", then the ungrant space should be
increase. In client, we should update cl_avail_grant only there
is OBD_MD_FLGRANT in the reply.
Severity : normal
Bugzilla : 14614
-Description: User code with malformed file open parameter crashes client node
+Description: User code with malformed file open parameter crashes client node
Details : Before packing join_file req, all the related reference should be
checked carefully in case some malformed flags cause fake
join_file req on client.
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
+ number of released locks which is not true for flock locks, so
just exclude such locks from consideration.
Severity : normal
Bugzilla : 11270
Description: eliminate client locks in face of contention
Details : file contention detection and lockless i/o implementation
- for contended files.
+ for contended files.
Severity : normal
Bugzilla : 15212
Bugzilla : 15574
Description: MDS LBUG: ASSERTION(!IS_ERR(dchild))
Details : Change LASSERTs to client eviction (i.e. abort client's recovery)
- because LASSERT on both the data supplied by a client, and the data
+ because LASSERT on both the data supplied by a client, and the data
on disk is dangerous and incorrect.
Severity : enhancement
and are never sent.
Severity : normal
-Bugzilla : 14629
-Description: filter threads hungs on waiting journal commit
+Bugzilla : 14629
+Description: filter threads hungs on waiting journal commit
Details : Cleanup filter group llog code, then only filter group llog will
be only created in the MDS/OST syncing process.
Severity : normal
-Bugzilla : 15684
-Description: Procfs and llog threads access destoryed import sometimes.
+Bugzilla : 15684
+Description: Procfs and llog threads access destoryed import sometimes.
Details : Sync the import destoryed process with procfs and llog threads by
the import refcount and semaphore.
Bugzilla : 14975
Description: openlock cache of b1_6 port to HEAD
+Severity : major
+Frequncy : rare
+Bugzilla : 16226
+Description: kernel BUG at ldiskfs2_ext_new_extent_cb
+Details : If insertion of an extent fails, then discard the inode
+ preallocation and free data blocks else it can lead to duplicate
+ blocks.
+
+Severity : normal
+Bugzilla : 16199
+Description: don't always update ctime in ext3_xattr_set_handle()
+Details : Current xattr code updates the inode ctime in ext3_xattr_set_handle.
+ In some cases the ctime should not be updated, for example for
+ 2.0->1.8 compatibility it is necessary to delete an xattr and it
+ should not update the ctime.
+
+Severity : major
+Frequency : rare
+Bugzilla : 15713/16362
+Description: Assertion in iopen_connect_dentry in 1.6.3
+Details : looking up an inode via iopen with the wrong generation number can
+ populate the dcache with a disconneced dentry while the inode
+ number is in the process of being reallocated. This causes an
+ assertion failure in iopen since the inode's dentry list contains
+ both a connected and disconnected dentry.
+
+Severity : normal
+Bugzilla : 16496
+Description: assertion failure in ldlm_handle2lock()
+Details : fix a race between class_handle_unhash() and class_handle2object()
+ introduced in lustre 1.6.5 by bug 13622.
+
+Severity : minor
+Frequency : rare
+Bugzilla : 12755
+Description: Kernel BUG: sd_iostats_bump: unexpected disk index
+Details : remove the limit of 256 scsi disks in the sd_iostat patch
+
+Severity : minor
+Frequency : rare
+Bugzilla : 16494
+Description: oops in sd_iostats_seq_show()
+Details : unloading/reloading the scsi low level driver triggers a kernel
+ bug when trying to access the sd iostat file.
+
+Severity : major
+Frequency : rare
+Bugzilla : 16404
+Description: Kernel panics during QLogic driver reload
+Details : REQ_BLOCK_PC requests are not handled properly in the sd iostat
+ patch, causing memory corruption.
+
+Severity : minor
+Frequency : rare
+Bugzilla : 16140
+Description: journal_dev option does not work in b1_6
+Details : pass mount option during pre-mount.
+
+Severity : enhancement
+Bugzilla : 10555
+Description: Add a FIEMAP(FIle Extent MAP) ioctl
+Details : FIEMAP ioctl will allow an application to efficiently fetch the
+ extent information of a file. It can be used to map logical blocks
+ in a file to physical blocks in the block device.
+
+Severity : normal
+Bugzilla : 15198
+Description: LDLM soft lockups - improvement
+Details : It is be possible to send the lock handle along with each read
+ or write request because the client is already doing a lock match
+ itself so there isn't any reason the OST should have to re-do that
+ search.
+
--------------------------------------------------------------------------------
2007-08-10 Cluster File Systems, Inc. <info@clusterfs.com>
Frequency : at statup only
Bugzilla : 12860
Description: mds_lov_synchronize race leads to various problems
-Details : simultaneous MDT->OST connections at startup can cause the
+Details : simultaneous MDT->OST connections at startup can cause the
sync to abort, leaving the OSC in a bad state.
Severity : enhancement
to update the client grant space info.
Severity : normal
-Frequency : when client reconnect to OST
+Frequency : when client reconnect to OST
Bugzilla : 11662
Description: Grant Leak when osc do resend and replay bulk write
Details : When osc reconnect to OST, OST(filter)should clear grant info of
these of resend/replay write req.
Severity : normal
-Frequency : rare
+Frequency : rare
Bugzilla : 11662
Description: Grant space more than avaiable left space sometimes.
Details : When then OST is about to be full, if two bulk writing from
different clients came to OST. Accord the avaliable space of the
OST, the first req should be permitted, and the second one
- should be denied by ENOSPC. But if the seconde arrived before
+ should be denied by ENOSPC. But if the seconde arrived before
the first one is commited. The OST might wrongly permit second
writing, which will cause grant space > avaiable space.
Severity : normal
-Frequency : when client is evicted
+Frequency : when client is evicted
Bugzilla : 12371
Description: Grant might be wrongly erased when osc is evicted by OST
-Details : when the import is evicted by server, it will fork another
- thread ptlrpc_invalidate_import_thread to invalidate the
- import, where the grant will be set to 0. While the original
- thread will update the grant it got when connecting. So if
- the former happened latter, the grant will be wrongly errased
+Details : when the import is evicted by server, it will fork another
+ thread ptlrpc_invalidate_import_thread to invalidate the
+ import, where the grant will be set to 0. While the original
+ thread will update the grant it got when connecting. So if
+ the former happened latter, the grant will be wrongly errased
because of this race.
Severity : normal
-Frequency : rare
+Frequency : rare
Bugzilla : 12401
-Description: Checking Stale with correct fid
-Details : ll_revalidate_it should uses de_inode instead of op_data.fid2
- to check whether it is stale, because sometimes, we want the
+Description: Checking Stale with correct fid
+Details : ll_revalidate_it should uses de_inode instead of op_data.fid2
+ to check whether it is stale, because sometimes, we want the
enqueue happened anyway, and op_data.fid2 will not be initialized.
Severity : enhancement
can be cause of random memory corruption.
Severity : normal
-Frequency : rare
+Frequency : rare
Bugzilla : 10818
Description: Memory leak in recovery
Details : Lov_mds_md was not free in an error handler in mds_create_object.
- It should also check obd_fail before fsfilt_start, otherwise if
+ It should also check obd_fail before fsfilt_start, otherwise if
fsfilt_start return -EROFS,(failover mds during mds recovery).
- then the req will return with repmsg->transno = 0 and rc = EROFS.
+ then the req will return with repmsg->transno = 0 and rc = EROFS.
and we met hit the assert LASSERT(req->rq_reqmsg->transno ==
- req->rq_repmsg->transno) in ptlrpc_replay_interpret. Fcc should
+ req->rq_repmsg->transno) in ptlrpc_replay_interpret. Fcc should
be freed no matter whether fsfilt_commit success or not.
Severity : minor
Frequency : only with huge count clients
Bugzilla : 11817
-Description: Prevents from taking the superblock lock in llap_from_page for
+Description: Prevents from taking the superblock lock in llap_from_page for
a soon died page.
-Details : using LL_ORIGIN_REMOVEPAGE origin flag instead of LL_ORIGIN_UNKNOW
- for llap_from_page call in ll_removepage prevents from taking the
+Details : using LL_ORIGIN_REMOVEPAGE origin flag instead of LL_ORIGIN_UNKNOW
+ for llap_from_page call in ll_removepage prevents from taking the
superblock lock for a soon died page.
Severity : normal
Frequency : rare
-Bugzilla : 11935
+Bugzilla : 11935
Description: Not check open intent error before release open handle
Details : in some rare cases, the open intent error is not checked before
release open handle, which may cause
Severity : normal
Frequency : rare
-Bugzilla : 12556
-Description: Set cat log bitmap only after create log success.
-Details : in some rare cases, the cat log bitmap is set too early. and it
+Bugzilla : 12556
+Description: Set cat log bitmap only after create log success.
+Details : in some rare cases, the cat log bitmap is set too early. and it
should be set only after create log success.
Severity : major
Severity : normal
Frequency : rare
-Bugzilla : 12086
-Description: the cat log was not initialized in recovery
+Bugzilla : 12086
+Description: the cat log was not initialized in recovery
Details : When mds(mgs) do recovery, the tgt_count might be zero, so the
unlink log on mds will not be initialized until mds post
- recovery. And also in mds post recovery, the unlink log will
+ recovery. And also in mds post recovery, the unlink log will
initialization will be done asynchronausly, so there will be race
between add unlink log and unlink log initialization.
Severity : normal
Bugzilla : 12689
Description: replay-single.sh test 52 fails
-Details : A lock's skiplist need to be cleanup when it being unlinked
+Details : A lock's skiplist need to be cleanup when it being unlinked
from its resource list.
Severity : normal
Severity : enhancement
Bugzilla : 12702
Description: refine locking for avoid write wrong info into lov_objid file
-Details : fix possible races with add new target and write/update data in
+Details : fix possible races with add new target and write/update data in
lov_objid file.
--------------------------------------------------------------------------------
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 beta5 (1.5.95).
+ version will not interoperate with 1.6 betas before beta5 (1.5.95).
* WARNING: Lustre configuration and startup changes are required with
this release. See https://mail.clusterfs.com/wikis/lustre/MountConf
for details.
Description: optimized stripe assignment
Details : stripe assignments are now made based on ost space available,
ost previous usage, and OSS previous usage, in order to try
- to optimize storage space and networking resources.
+ to optimize storage space and networking resources.
Severity : enhancement
Bugzilla : 4226
Bugzilla : 22484
Description: client read/write statistics
Details : Add client read/write call usage stats for performance
- analysis of user processes.
+ analysis of user processes.
/proc/fs/lustre/llite/*/offset_stats shows non-sequential
file access. extents_stats shows chunk size distribution.
extents_stats_per_process show chunk size distribution per
- user process.
+ user process.
Severity : enhancement
Bugzilla : 22486
Description: mds statistics
-Details : Add detailed mds operations statistics in
+Details : Add detailed mds operations statistics in
/proc/fs/lustre/mds/*/stats.
Severity : minor
Frequency : Rare
Bugzilla : 11248
Description: merge and cleanup kernel patches.
-Details :
+Details :
-----------------------------------------------------------------------------
git://git.whamcloud.com / fs / lustre-release.git / blobdiff