=Changes from v1.6.4.1 to v1.6.4.2=

'''Support for kernels: 2.6.5-7.286 (SLES 9), 2.6.9-55.0.9.EL (RHEL 4), 2.6.16.53-0.8 (SLES 10), 2.6.18-8.1.14.el5 (RHEL 5), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to problems with nested symlinks and FMODE_EXEC (bug 12652), we do not recommend using patchless RHEL4 clients with kernels prior to 2.6.9-55EL (RHEL4U5).'''

'''Recommended e2fsprogs version: 1.40.4-cfs1'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.'''

'''RHEL 4 (patched) and RHEL 5/SLES 10 (patchless) clients behave differently on 'cd' to a removed cwd "./" (refer to Bugzilla 14399).'''

*Severity: critical

Frequency: only for relatively new filesystems, when OSTs are in recovery

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=14631 14631 ]

Description: OST objects below id 20000 are deleted, causing data loss

Details: For relatively newly formatted OST filesystem(s), where there have not been at least 20000 objects created on an OST a bug in MDS->OST orphan recovery could cause those objects to be deleted if the OST was in recovery, but the MDS was not. Safety checks in the orphan recovery prevent this if more than 20000 objects were ever created on an OST. If the MDS was also in recovery the problem was not hit. Only in 1.6.4.1.

*Severity: major

Frequency: rare, depends on device drivers and load

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=14529 14529]

Description: MDS or OSS nodes crash due to stack overflow

Details: Code changes in 1.6.4 increased the stack usage of some functions. In some cases, in conjunction with device drivers that use a lot of stack the MDS (or possibly OSS) service threads could overflow the stack. One change which was identified to consume additional stack has been reworked to avoid the extra stack usage.

=Changes from v1.6.4 to v1.6.4.1=

'''Support for networks: socklnd - any kernel supported by Lustre, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1 and 1.2, viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

'''Support for kernels: 2.6.5-7.286 (SLES 9), 2.6.9-55.0.9.EL (RHEL 4), 2.6.16.53-0.8 (SLES 10), 2.6.18-8.1.14.el5 (RHEL 5), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to recently discovered recovery problems, we do not recommend using patchless RHEL 4 clients with this or any earlier release.'''

'''Recommended e2fsprogs version: 1.40.2-cfs1'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.'''

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=14433 14433]

Description: Oops on connection from 1.6.3 client

Frequency: always, on connection from 1.6.3 client

Details: Enable and accept the OBD_CONNECT_LRU_RESIZE flag only if LRU resizing is enabled at configure time. This fixes an oops caused by incorrectly accepting the LRU_RESIZE feature even if --enable-lru-resize is not specified.

=Changes from v1.6.3 to v1.6.4=

'''Support for networks: socklnd - any kernel supported by Lustre, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1 and 1.2, viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

'''Support for kernels: 2.6.5-7.286 (SLES 9), 2.6.9-55.0.9.EL (RHEL 4), 2.6.16.53-0.8 (SLES 10), 2.6.18-8.1.14.el5 (RHEL 5), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to recently discovered recovery problems, we do not recommend using patchless RHEL 4 clients with this or any earlier release.'''

'''Recommended e2fsprogs version: 1.40.2-cfs1'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11686 11686]

Description: Console message flood

Details: Make cdls ratelimiting more tunable by adding several tunable in procfs /proc/sys/lnet/console_{min,max}_delay_centisecs and /proc/sys/lnet/console_backoff.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13521 13521]

Description: Update kernel patches for SLES10 2.6.16.53-0.8.

Details: Update which_patch & target file for SLES10 latest kernel.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13128 13128]

Description: add --type and --size parameters to lfs find

Details: Enhance lfs find by adding filetype and filesize parameters. Also multiple OBDs can now be specified for the --obd option.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11270 11270]

Description: eliminate client locks in face of contention

Details: file contention detection and lockless i/o implementation for contended files.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12411 12411]

Description: Remove client patches from SLES 10 kernel.

Details: This causes SLES 10 clients to behave as patchless clients even on a Lustre-patched (server) kernel.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=2369 2369 ]

Description: use i_size_read and i_size_write in 2.6 port

Details: replace inode->i_size access with i_size_read/write()

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13454 13454]

Description: Add jbd statistics patch for RHEL5 and 2.6.18-vanilla.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13518 13518]

Description: Kernel patches update for RHEL4 2.6.9-55.0.6.

Details: Modify vm-tunables-rhel4.patch.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13452 13452]

Description: Kernel config for 2.6.18-vanilla.

Details: Modify targets/2.6-vanilla.target.in. Add config file kernel-2.6.18-2.6-vanilla-i686.config. Add config file kernel-2.6.18-2.6-vanilla-i686-smp.config. Add config file kernel-2.6.18-2.6-vanilla-x86_64.config. Add config file kernel-2.6.18-2.6-vanilla-x86_64-smp.config.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13207 13207]

Description: adapt the lustre_config script to support the upgrade case

Details: Add "-u" option for lustre_config script to support upgrading 1.4 server targets to 1.6 in parallel.

*Severity: critical

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13751 13751]

Description: Kernel patches update for RHEL5 2.6.18-8.1.14.el5.

Details: Modify target file & which_patch. A flaw was found in the IA32 system call emulation provided on AMD64 and Intel 64 platforms. An improperly validated 64-bit value could be stored in the %RAX register, which could trigger an out-of-bounds system call table access. An untrusted local user could exploit this flaw to run code in the kernel (ie a root privilege escalation). (CVE-2007-4573).

*Severity: critical

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13748 13748]

Description: Update RHEL 4 kernel to fix local root privilege escalation.

Details: Update to the latest RHEL 4 kernel to fix the vulnerability described in CVE-2007-4573. This problem could allow untrusted local users to gain root access.

*Severity: major

Frequency: occasional

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=14353 14353]

Description: excessive CPU consumption on client reduces IO performance

Details: in some cases the ldlm_poold thread is spending too much time trying to cancel locks, and is cancelling them too aggressively and this can severely impact IO performance. Disable the dynamic LRU resize code at build time. It can be re-enabled with configure --enable-lru-resize at build time.

*Severity: major

Frequency: occasional

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13917 13917]

Description: MDS hang or stay in waiting lock

Details: If client receive lock with CBPENDING flag ldlm need send lock cancel as separate rpc, to avoid situation when cancel request can't processed due all i/o threads stay in wait lock.

*Severity: major

Frequency: occasional

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11710 11710]

Description: improve handling recoverable errors
Details: If request processed with error which can be recoverable on server request should be resend, otherwise page released from cache and marked as error.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12302 12302]

Description: new userspace socklnd

Details: Old userspace tcpnal that resided in lnet/ulnds/socklnd replaced with new one - usocklnd.

*Severity: normal

Frequency: occasional

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13730 13730]

Description: Do not fail import if osc_interpret_create gets -EAGAIN

Details: If osc_interpret_create got -EAGAIN it immediately exits and wakeup oscc_waitq. After wakeup oscc_wait_for_objects call oscc_has_objects and see OSC has no objests and call oscc_internal_create to resend create request.

*Severity: normal

Frequency: when removing large files

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13181 13181]

Description: scheduling issue during removal of large Lustre files

Details: Don't take the BKL in fsfilt_ext3_setattr() for 2.6 kernels. It causes scheduling issues when removing large files (17TB in the present case).

*Severity: normal

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13358 13358]

Description: 1.4.11 Can't handle directories with stripe set and extended ACLs

Details: Impossible (EPROTO is returned) to access a directory that has a non-default striping and ACLs.

*Severity: normal

Frequency: only on ppc

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12234 12234]

Description: /proc/fs/lustre/devices broken on ppc

Details: The patch as applied to 1.6.2 doesn't look correct for all arches. We should make sure the type of 'index' is loff_t and then cast explicitly as needed below. Do not assign an explicitly cast loff_t to an int.

*Severity: normal

Frequency: only for rhel5

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13616 13616]

Description: Kernel patches update for RHEL5 2.6.18-8.1.10.el5.

Details: Modify the target file & which_kernel.

*Severity: normal

Frequency: if the uninit_groups feature is enabled on ldiskfs

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13706 13706]

Description: e2fsck reports "invalid unused inodes count"

Details: If a new ldiskfs filesystem is created with the "uninit_groups" feature and only a single inode is created in a group then the "bg_unused_inodes" count is incorrectly updated. Creating a second inode in that group would update it correctly.

*Severity: normal

Frequency: only if filesystem is inconsistent

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11673 11673]

Description: handle "serious error: objid * already exists" more gracefully

Details: If LAST_ID value on disk is smaller than the objects existing in the O/0/d* directories, it indicates disk corruption and causes an LBUG(). If the object is 0-length, then we should use the existing object. This will help to avoid a full fsck in most cases.

*Severity: normal

Frequency: rarely

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13570 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 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 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

Frequency: when using O_DIRECT and quotas

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13930 13930]

Description: Incorrect file ownership on O_DIRECT output files

Details: block usage reported by 'lfs quota' does not take into account files that have been written with O_DIRECT.

*Severity: normal

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13976 13976]

Description: touch file failed when fs is not full

Details: OST in recovery should not be discarded by MDS in alloc_qos(), otherwise we can get ENOSP while fs is not full.

*Severity: normal

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13805 13805]

Description: data checksumming impacts single node performance

Details: disable checksums by default since it impacts single node performance. It is still possible to enable checksums by default via "configure --enable-checksum", or at runtime via procfs.

*Severity: minor

Frequency: when lov objid is destroyed

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=14222 14222]

Description: mds can't recreate lov objid file.

Details: if lov objid file is destroyed and ost with highest index connected first mds not get last objid number from ost. Also if mds get last id from ost his not tell osc about this and it's produce warning about wrong del orphan request.

*Severity: minor

Frequency: rarely

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12948 12948]

Description: buffer overruns could theoretically occur

Details: llapi_semantic_traverse() modifies the "path" argument by appending values to the end of the origin string, and a buffer overrun may occur. Adding buffer overrun check in liblustreapi.

*Severity: minor

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13732 13732]

Description: change order of libsysio includes

Details: '#include sysio.h' should always come before '#include xtio.h'

=Changes from v1.6.2 to v1.6.3=

'''Support for networks: socklnd - any kernel supported by Lustre, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1 and 1.2, viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

'''Support for kernels: 2.6.5-7.286 (SLES 9), 2.6.9-55.0.2.EL (RHEL 4), 2.6.16.46-0.14 (SLES 10), 2.6.18-8.1.8.el5 (RHEL 5), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to recently discovered recovery problems, we do not recommend using patchless RHEL 4 clients with this or any earlier release.'''

'''Recommended e2fsprogs version: 1.40.2-cfs1'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12192 12192]

Description: llapi_file_create() does not allow some changes

Details: add llapi_file_open() that allows specifying the file creation mode and open flags, and also returns an open file handle.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12743 12743]

Description: df doesn't work properly if diskfs blocksize != 4K

Details: Choose biggest blocksize of OST's as the LOV's blocksize.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11248 11248]

Description: merge and cleanup kernel patches.

Details: Remove mnt_lustre_list in vfs_intent-2.6-rhel4.patch.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13039 13039]

Description: RedHat Update kernel for RHEL5

Details: Kernel config file for RHEL5.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12446 12446]

Description: OSS needs mutliple precreate threads

Details: Add ability to start more than one create thread per OSS.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13039 13039]

Description: RedHat Update kernel for RHEL5

Details: Modify the kernel config file more closer RHEL5.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13360 13360]

Description: Build failure against Centos5 (RHEL5)

Details: Define PAGE_SIZE when it isn't present.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11401 11401]

Description: client-side metadata stat-ahead during readdir(directory readahead)

Details: perform client-side metadata stat-ahead when the client detects readdir and sequential stat of dir entries therein

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11230 11230]

Description: Tune the kernel for good SCSI performance.

Details: Set the value of /sys/block/{dev}/queue/max_sectors_kb to the value of /sys/block/{dev}/queue/max_hw_sectors_kb in mount_lustre.

*Severity: critical

Frequency: Always for filesystems larger than 2TB on 32-bit systems.

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13547 13547] , [https://bugzilla.lustre.org/show_bug.cgi?id=13627 13627]

Description: Data corruption for OSTs that are formatted larger than 2TB on 32-bit servers.

Details: When generating the bio request for lustre file writes the sector number would overflow a temporary variable before being used for the IO. The data reads correctly from Lustre (which will overflow in a similar manner) but other file data or filesystem metadata may be corrupted in some cases.

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13236 13236]

Description: TOE Kernel panic by ksocklnd

Details: offloaded sockets provide their own implementation of sendpage, can't call tcp_sendpage() directly

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13482 13482]

Description: build error

Details: fix typos in gmlnd, ptllnd and viblnd

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12932 12932]

Description: obd_health_check_timeout too short

Details: set obd_health_check_timeout as 1.5x of obd_timeout

*Severity: major

Frequency: only with quota on the root user

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12223 12223]

Description: mds_obd_create error creating tmp object

Details: When the user sets quota on root, llog will be affected and can't create files and write files.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12782 12782]

Description: /proc/sys/lnet has non-sysctl entries

Details: Updating dump_kernel/daemon_file/debug_mb to use sysctl variables

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10778 10778]

Description: kibnal_shutdown() doesn't finish; lconf --cleanup hangs

Details: races between lnd_shutdown and peer creation prevent lnd_shutdown from finishing.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13279 13279]

Description: open files rlimit 1024 reached while liblustre testing

Details: ulnds/socklnd must close open socket after unsuccessful 'say hello' attempt.

*Severity: normal

Frequency: always on directories with default striping set

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12836 12836]

Description: lfs find on -1 stripe looping in lsm_lmm_verify_common()

Details: Avoid lov_verify_lmm_common() on directory with -1 stripe count.

*Severity: normal

Frequency: Always on ia64 patchless client, and possibly others.

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12826 12826]

Description: Add EXPORT_SYMBOL check for node_to_cpumask symbol.

Details: This allows the patchless client to be loaded on architectures without this export.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13142 13142]

Description: disorder of journal start and llog_add cause deadlock.

Details: in llog_origin_connect, journal start should happen before llog_add keep the same order as other functions to avoid the deadlock.

*Severity: normal

Frequency: occasionally when using NFS

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13030 13030]

Description: "ll_intent_file_open()) lock enqueue: err: -13" with nfs

Details: with NFS, the anon dentry's parent was set to itself in d_alloc_anon(), so in MDS, we use rec->ur_fid1 to find the corresponding dentry other than use rec->ur_name.

*Severity: normal

Frequency: Occasionally with failover

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12459 12459]

Description: Client eviction due to failover config

Details: after a connection loss, the lustre client should attempt to reconnect to the last active server first before trying the other potential connections.

*Severity: normal

Frequency: only with liblustre clients on XT3

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12418 12418]

Description: evictions taking too long

Details: allow llrd to evict clients directly on OSTs

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13125 13125]

Description: osts not allocated evenly to files

Details: change the condition to increase offset_idx

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13436 13436]

Description: Only those disconnect error should be returned by rq_status.

Details: In open/enqueue processs, Some errors, which will cause client disconnected, should be returned by rq_status, while other errors should still be returned by intent, then mdc or llite will detect them.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13600 13600]

Description: "lfs find -obd UUID" prints directories

Details: "lfs find -obd UUID" will return all directory names instead of just file names. It is incorrect because the directories do not reside on the OSTs.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13596 13596]

Description: MDS hang after unclean shutdown of lots of clients

Details: Never resend AST requests.

*Severity: normal

Frequency: Always, for kernels after 2.6.16

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13304 13304]

Description: Fix warning idr_remove called for id=.. which is not allocated.
Details: Last kernels save old s_dev before kill super and not allow to restore from callback - restore it before call kill_anon_super.

*Severity: minor

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12186 12186]

Description: Fix errors in lfs documentation

Details: Fixes man pages

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12588 12588]

Description: when mds and osts use different quota unit(32bit and 64bit), quota will be released repeatly.

Details: void sending multiple quota reqs to mds, which will keep the status between the reqs.

*Severity: cleanup

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13532 13532]

Description: rewrite ext2-derived code in llite/dir.c and obdclass/uuid.c

Details: rewrite inherited code (uuid parsing code from ext2 utils and readdir code from ext3) from scratch preserving functionality.

=Changes from v1.6.1 to v1.6.2=

'''Support for kernels: 2.6.5-7.286 (SLES 9), 2.6.9-55.0.2.EL (RHEL 4), 2.6.16.46-0.14 (SLES 10), 2.6.18-8.1.8.el5 (RHEL 5), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?
title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to recently discovered recovery problems, we do not recommend using patchless RHEL 4 clients with this or any earlier release.'''

'''Recommended e2fsprogs version: 1.39.cfs8'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12786 12786]

Description: lfs setstripe enhancement

Details: Make lfs setstripe understand 'k', 'm' and 'g' for stripe size.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12211 12211]

Description: randomly memory allocation failure util

Details: Make lustre randomly failed allocating memory for testing purpose.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10786 10786]

Description: omit set fsid for export NFS

Details: fix set/restore device id for avoid EMFILE error and mark lustre fs as FS_REQUIRES_DEV for avoid problems with generate fsid.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10595 10595]

Description: Error message improvement.

Details: Merging of two LCONSOLE_ERROR_MSG into one.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12602 12606]

Description: don't use GFP_* in generic Lustre code.

Details: Use cfs_alloc_* functions and CFS_* flags for code portability.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12333 12333]

Description: obdclass is limited by single OBD_ALLOC(idarray)

Details: replace OBD_ALLOC/OBD_FREE with OBD_VMALLOC/OBD_VFREE

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12415 12415 ]

Description: updated patchess for new RHEL4 kernel

Details: Fixed ext3-unlink-race.patch per Kalpak's comment.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13006 13006 ]

Description: warnings with build patchless client with vanila 2.6.19 and up

Details: change old ctl_table style and replace ctl_table/ctl_table_header with cfs_sysctl_table_t/cfs_sysctl_table_header_t

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13093 13093]

Description: O_DIRECT bypasses client statistics.

Details: When running with O_DIRECT I/O, neither the client rpc_stats nor read_ahead_stats were updated. Copied stats section from osc_send_oap_rpc() into async_internal().

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13249 13249]

Description: Kernel patches for SLES9 2.6.5-7.286 kernel

Details: Update target/ChangeLog/which_patch .

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12955 12955]

Description: jbd statistics

Details: Port older jbd statistics patch for sles10

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13360 13360]

Description: Build failure against Centos5 (RHEL5)

Details: Use getpagesize() instead of PAGE_SIZE.

*Severity: major

Frequency: after network failures

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12769 12769]

Description: Add sync option to mount_lustre.c

Details: Client loses data written to lustre after a network interruption.

*Severity: normal

Frequency: mds/oss recovery

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10800 10800]

Description: llog ctxt is refrenced after it has been freed.

Details: llog ctxt refcount was added to avoide the race between ctxt free and llog recovery process. Each llog user must hold ctxt refcount before it access the llog. And the llog ctxt can only be freed when its refcount is zero.

*Severity: normal

Frequency: only for SLES10

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12771 12771]

Description: Update kernel patch for SLES10 SP1

Details: Add patch blkdev_tunables-2.6-sles10.patch to 2.6-sles10.series.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11802 11802]

Description: lustre support for RHEL5

Details: Add support for RHEL5.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11756 11756]

Description: umount blocks forever on error

Details: In result of wrong using obd_no_recov and obd_force flags client can hand if cancel or some other requests is lost.

*Severity: normal

Frequency: Only for SLES

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13177 13177]

Description: sanity_quota fail test_1

Details: There are multiple occurences of $TSTUSR in SLES's /etc/group file, which makes TSTID[2] inunique.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9977 9977]

Description: lvbo_init failed for resource with missing objects.

Details: Fix returning error if we do stat for file with missing/corrupted objects and i_size set to all sum of size of all avaible objects. if we to truncate/write to missing object - it is recreated.

*Severity: normal

Frequency: When flocks are used.

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13103 13103]

Description: assertion failure in ldlm_cli_enquque_fini for non NULL lock.

Details: Flock locks might destroy just granted lock if it could be merged with another existing flock, this is done in completion handler, so teach ldlm_cli_enquque_fini that this is a valid case for flock locks.

*Severity: normal

Frequency: Rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11974 11974]

Description: reply_lock_interpret crash due to race with it and lock cancel.

Details: Do not replay locks that are being cancelled. Do not reference locks by their address during replay, just by their handle.

*Severity: normal

Frequency: only with deactivated OSTs

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11679 11679]

Description: lstripe command fails for valid OST index

Details: The stripe offset is compared to 'lov->desc.ld_tgt_count' instead of lov->desc.ld_active_tgt_count.

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13147 13147]

Description: block reactivating mgc import until all deactivates complete

Details: Fix race when failing back MDT/MGS to itself (testing)

*Severity: minor

Frequency: only for Cray XT3

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11706 11706]

Description: peer credits not enough on many OST per OSS systems.

Details: Use new lnet way to add credits as we need those for pings and ASTs

*Severity: minor

Frequency: only with liblustre

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12790 12790]

Description: Liblustre is not releasing flock locks on file close.

Details: Release flock locks on file close.

*Severity: minor

Frequency: only for RHEL4

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12839 12839]

Description: Update kernel patches for kernel-2.6.9-55.0.2.EL

Details: Remove inode-nr_unused-2.6.9-rhel4.patch from 2.6-rhel4.series Update target file and kernel config.

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11327 11327 ]

Description: ASSERTION(export != NULL) failed in target_handle_connect

Details: Assetion hit is result of rare race between disconnect and connet to same nid. target_handle_connect found old connect cockie and tried to reconnect, but can't find export for this cockie.

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13276 13276]

Description: Oops in read and write path when failing to allocate lock.

Details: Check if lock allocation failed and return error back.

=Changes from v1.6.0.1 to v1.6.1=

'''Support for networks: socklnd - kernels up to 2.6.16, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1 and 1.2 viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

'''Support for kernels: 2.6.5-7.283 (SLES 9), 2.6.9-55.EL (RHEL 4), 2.6.16.46-0.14 (SLES 10), 2.6.18.8 vanilla (kernel.org)'''

'''Client support for unpatched kernels: (see http://wiki.lustre.org/index.php?title=Patchless_Client) 2.6.16 - 2.6.22 vanilla (kernel.org)'''

'''Due to recently discovered recovery problems, we do not recommend using patchless RHEL 4 clients with this or any earlier release.'''

'''Recommended e2fsprogs version: 1.39.cfs8'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel.
Starting with this release, the ldiskfs backing filesystem required by Lustre is now in its own package, lustre-ldiskfs. This package should be installed. It is versioned separately from Lustre and may be released separately in future.'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12194 12194]

Description: add optional extra BUILD_VERSION info

Details: add a new environment variable (namely LUSTRE_VERS) which allows to override the lustre version.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11548 11548]

Description: Add LNET router traceability for debug purposes

Details: If a checksum failure occurs with a router as part of the IO path, the NID of the last router that forwarded the bulk data is printed so it can be identified.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10997 10997]

Description: lfs setstripe use optional parameters instead of postional parameters.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10651 10651]

Description: Nanosecond timestamp support for ldiskfs

Details: The on-disk ldiskfs filesystem has added support for nanosecond resolution timestamps. There is not yet support for this at the Lustre filesystem level.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10768 10768]

Description: 64-bit inode version

Details: : Add a on-disk 64-bit inode version for ext3 to track changes made to the inode. This will be required for version-based recovery.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11563 11563]

Description: Add -o localflock option to simulate old noflock behaviour.

Details: This will achieve local-only flock/fcntl locks coherentness.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11647 11647]

Description: update patchless client

Details: Add support for patchless client with 2.6.20, 2.6.21 and RHEL 5

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10589 10589]

Description: metadata RPC reduction (e.g. for rm performance)

Details: decrease the amount of synchronous RPC between clients and servers by canceling conflicing lock before the operation on the client and packing thier handles into the main operation RPC to server.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12605 12605]

Description: add #ifdef HAVE_KERNEL_CONFIG_H

Details: kernels from 2.6.19 not need include linux/config.h, but add include linux/autoconf.h in commpiler command line.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12764 12764]

Description: patchless client support for 2.6.22 kernel

Details: 2.6.22 has only one visble change, SLAB_CTOR_* constants is removed. In this case we need drop using os depended interface to kmem_cache and use cfs_mem_cache API.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10968 10968]

Description: VFS operations stats tool.

Details: Tool which collects stats by tracking value written in pid, ppid, gid and uses llstat to generate output to plot graph using plot-llstat Updated lustre/utils/Makefile.am Added lustre/utils/ltrack_stats.c

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11039 11039]

Description: 2.6.18 server support (lustre 1.6.1)

Details: Support for 2.6.18 kernels on the server side.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12678 12678]

Description: remove fs_prep_san_write operation and related patches

Details: remove the ext3-san-jdike patches which are no longer useful.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=4900 4900]

Description: Async OSC create to avoid the blocking unnecessarily.

Details: If a OST has no remain object, system will block on the creating when need to create a new object on this OST. Now, ways use pre-created objects when available, instead of blocking on an empty osc while others are not empty. If we must block, we block for the shortest possible period of time.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11721 11721]

Description: Add printing inode info into message about error in writepage.

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11971 11971]

Description: Accessing a block bevice can re-enable I/O when Lustre is tearing down a device.

Details: dev_clear_rdonly(bdev) must be called in kill_bdev() instead of blkdev_put().

*Severity: major

Frequency: only with mballoc3 code and deep extent trees

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12861 12861]

Description: ldiskfs_ext_search_right: bad header in inode: unexpected eh_depth

Details: a wrong check of extent headers in ldiskfs_ext_search_right() can cause the filesystem to be remounted read-only.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13129 13129]

Description: server LBUG when shutting down

Details: Block umount forever until the mount refcount is zero rather than giving up after an arbitrary timeout.

*Severity: normal

Frequency: 2.6.18 servers only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12546 12546 ]

Description: ll_kern_mount() doesn't release the module reference

Details: The ldiskfs module reference count never drops down to 0 because ll_kern_mount() doesn't release the module reference.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12470 12470]

Description: server LBUG when using old ost_num_threads parameter

Details: Accept the old ost_num_threads parameter but warn that it is deprecated, and fix an off-by-one error that caused an LBUG.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11722 11722]

Description: Transient SCSI error results in persistent IO issue

Details: iobuf->dr_error is not reinitialized to 0 between two uses.

*Severity: normal

Frequency: sometimes when underlying device returns I/O errors

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11743 11743]

Description: OSTs not going read-only during write failures

Details: OSTs are not remounted read-only when the journal commit threads get I/O errors because fsfilt_ext3 calls journal_start/stop() instead of the ext3 wrappers.

*Severity: normal

Frequency: SLES10 only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12538 12538]

Description: sanity-quota.sh quotacheck failed: rc = -22

Details: Quotas cannot be enabled on SLES10.

*Severity: normal

Frequency: liblustre clients only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12229 12229]

Description: getdirentries does not give error when run on compute nodes

Details: getdirentries does not fail when the size specified as an argument is too small to contain at least one entry

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11315 11315]

Description: OST "spontaneously" evicts client; client has imp_pingable == 0

Details: Due to a race condition, liblustre clients were occasionally evicted incorrectly.

*Severity: normal

Frequency: during server recovery

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11203 11203]

Description: MDS failing to send precreate requests due to OSCC_FLAG_RECOVERING

Details: request with rq_no_resend flag not awake l_wait_event if they get a timeout.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11818 11818]

Description: MDS fails to start if a duplicate client export is detected

Details: in some rare cases it was possible for a client to connect to an MDS multiple times. Upon recovery the MDS would detect this and fail during startup. Handle this more gracefully.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12477 12477]

Description: Wrong request locking in request set processing

Details: ptlrpc_check_set wrongly uses req->rq_lock for proctect add to imp_delayed_list, in this place should be used imp_lock.

*Severity: normal

Frequency: when reconnecting

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11662 11662]

Description: Grant leak when OSC reconnect to OST

Details: When osc reconnect ost, OST(filter) should check whether it should grant more space to client by comparing fed_grant and cl_avail_grant, and return the granted space to client instead of "new granted" space, because client will call osc_init_grant to update the client grant space info.

*Severity: normal

Frequency: when client reconnects to OST

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11662 11662]

Description: Grant leak when OSC does a resend and replays bulk write

Details: When osc reconnect to OST, OST(filter) should clear grant info of bulk write request, because the grant info while be sync between OSC and OST when reconnect, and we should ignore the grant info these of resend/replay write req.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11662 11662]

Description: Grant space more than avaiable 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 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

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12371 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 because of this race.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12401 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 enqueue happened anyway, and op_data.fid2 will not be initialized.

*Severity: normal

Frequency: only with 2.4 kernel

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12134 12134]

Description: random memory corruption

Details: size of struct ll_inode_info is to big for union inode.u and this can be cause of random memory corruption.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10818 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 fsfilt_start return -EROFS,(failover mds during mds recovery). 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 be freed no matter whether fsfilt_commit success or not.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11935 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 ASSERTION(open_req->rq_transno != 0), because it tries to release the failed open handle.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12556 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: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12086 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 initialization will be done asynchronausly, so there will be race between add unlink log and unlink log initialization.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12579 12597]

Description: brw_stats were being printed incorrectly

Details: brw_stats were being printed as log2 but all of them were not recorded as log2. Also remove some code duplication arising from filter_tally_{read,write}.

*Severity: normal

Frequency: rare, only in recovery.

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11674 11674]

Description: ASSERTION(req->rq_type != LI_POISON) failed

Details: imp_lock should be held while iterating over imp_sending_list for prevent destroy request after get timeout in ptlrpc_queue_wait.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12689 12689]

Description: replay-single.sh test 52 fails

Details: A lock's skiplist need to be cleanup when it being unlinked from its resource list.

*Severity: normal

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11737 11737]

Description: Short directio read returns full requested size rather than
actual amount read.

Details: Direct I/O operations should return actual amount of bytes transferred rather than requested size.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12646 12646]

Description: sanity.sh test_77h fails with "test_77h file compare failed"

Details: test_77h uses a file which was messed by other test case.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12576 12576]

Description: Not Check whether lov_tgts is NULL in some lov functions

Details: Checking whether lov_tgts is NULL in some functions.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11815 11815]

Description: replace obdo_alloc() with OBDO_ALLOC macro

Details: nothing special is done in obdo_alloc() function, and for debugging purpose, it needs to be replaced with macros.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12784 12784]

Description: bad return value and errno from fcntl call

Details: In liblustre API, errno should be a negative value if error happens.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11544 11544]

Description: ptlrpc_check_set() LBUG

Details: In case of positive reply from server and failed client bulk callback after bulk transfer shouldn't LBUG, but process this request as erroneous.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12696 12696]

Description: ASSERTION(imp->imp_conn_current) failed

Details: an assertion failure is hit if a client node boots and attempts to mount a lustre filesystem faster than RECONNECT_INTERVAL seconds.

*Severity: normal

Frequency: only for i686

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12695 12695]

Description: 1.4.11 RC1 build fails for RHEL 4, i686

Details: Fixed config variable for build.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12415 12415]

Description: Updated patchess for new RHEL4 kernel

Details: Updated patch inode-nr_unused-2.6.9-rhel4.patch Updated patch jbd-stats-2.6.9.patch Updated patch qsnet-rhel4-2.6.patch Updated patch quota-deadlock-on-pagelock-core.patch Updated patch vfs_intent-2.6-rhel4.patch Updated patch vfs_races-2.6-rhel4.patch Updated series file 2.6-rhel4-titech.series Updated series file 2.6-rhel4.series Updated kernel config files

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12374 12374]

Description: lquota slave complains LBUG when reconnecting with mds or
failover in mds.

Details: quota slave depends qctxt->lqc_import to send its quota request. This pointer will be invalid if mds did failover or broke its connect to osts, which leads to LBUG.

*Severity: normal

Frequency: when qunit size is too small(less than 20M)

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12588 12588]

Description: write is stopped by improper -EDQUOT

Details: If the master is busy and qunit size is small enough(let's say 1M), the slave can not get quota from master on time, which will lead slave to trigger a -EQUOTA to client.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12629 12629]

Description: Deadlock during metadata tests

Details: in prune_dir_dentries(), shrink_dcache_parent() should not be called with the per-dentry lock held.

*Severity: normal

Frequency: SLES9 only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12744 12744]

Description: Lustre patched kernel for SLES9 SP3 has NR_CPUS set to 8

Details: set CONFIG_NR_CPUS to 128 instead of 8.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11324 11324]

Description: LDISKFS-fs error (device sdc): ldiskfs_free_blocks

Details: a disk corruption can cause the mballoc code to assert on a double free or other extent corruptions. Handle these with ext3_error() instead of assertions.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13063 13063]

Description: lfsck built against 1.4.x cannot run against 1.6.0 lustre

Details: the definition for OBD_IOC_GETNAME changed in 1.6.0. One of the few external users of this ioctl number is lfsck's call to llapi_lov_get_uuids() and this caused lfsck to fail at startup. Add the old ioctl number to the handler so both old and new lfsck can work.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11301 11301]

Description: parallel lock callbacks

Details: Instead of sending blocking and completion callbacks as separated requests, adding them to a set and sending in parallel.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12417 12417]

Description: Disable most debugging by default

Details: To improve performance, disable most logging (for debug purposes) by default. VFSTRACE, RPCTRACE, and DLMTRACE are now off by default, and HA includes fewer messages.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11013 11013]

Description: hash tables for lists of nids, connections and uuids

Details: Hash tables noticeably help when a lot of clients connect to a server, to faster identify duplicate connections or reconnects, also to faster find export to evict in manual eviction case.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11190 11190]

Description: Sometimes, when the server evict a client, and the client will not be evicted as soon as possible.

Details: In enqueue req, the error was returned by intent, instead of rq_status which make ptlrpc layer not detect this error, and does not evict the client. So enqueue error should be returned by rq_status.

*Severity: normal

Frequency: only for SLES9

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12543 12543]

Description: Routinely utilize latest Quadrics drivers in CFS releases

Details: Update patch qsnet-suse-2.6.patch.

*Severity: normal

Frequency: only for sles10

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12771 12771]

Description: Update patches for SLES 10 SP1 kernel.

Details: Update the patch vfs_intent-2.6-sles10.patch.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12543 12543]

Description: Routinely utilize latest Quadrics drivers in CFS releases

Details: Update patch qsnet-rhel4-2.6.patch.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12975 12975]

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

*Severity: normal

Frequency: only in recovery

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13148 13148]

Description: Mark OST as early accessible if his start SYNC.

Details: osc_precreate return flag early accessible if oscc marked as OSCC_FLAG_SYNC_IN_PROGRESS.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13196 13196]

Description: Sometimes precreate code can triger create object on wrong ost

Details: Wrong protected or not not restored variables aftre precreate loop can produce creation object on wrong ost.

*Severity: normal

Frequency: oss recovery

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10800 10800]

Description: llog_commit_thread cleanup should sync with llog_commit_thread
start

Details: llog_commit_thread_count should be synced between llog_commit start and cleanup, so new llog_commit thread should not be started when llog_commit threads being stopped to avoid accessing some freed stuff.

*Severity: minor

Frequency: only with 10000 clients or more

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12364 12364]

Description: poor connect scaling with increasing client count

Details: Don't run filter_grant_sanity_check for more than 100 exports to improve scaling for large numbers of clients.

*Severity: minor

Frequency: nfs export on patchless client

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11970 11970]

Description: connectathon hang when test nfs export over patchless client

Details: Disconnected dentry cannot be found with lookup, so we do not need to unhash it or make it invalid

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11546 11546]

Description: open req refcounting wrong on reconnect

Details: If reconnect happened between getting open reply from server and call to mdc_set_replay_data in ll_file_open, we will schedule replay for unreferenced request that we are about to free. Subsequent close will crash in variety of ways. Check that request is still eligible for replay in mdc_set_replay_data().

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11512 11512]

Description: disable writes to filesystem when reading health_check file

Details: the default for reading the health_check proc file has changed to NOT do a journal transaction and write to disk, because this can cause reads of the /proc file to hang and block HA state checking on a healthy but otherwise heavily loaded system. It is possible to return to the previous behaviour during configure with --enable-health-write.

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11658 11658 ]

Description: log_commit_thread vs filter_destroy race leads to crash

Details: Take import reference before releasing llog record semaphore

*Severity: minor

Frequency: only with huge numbers of clients

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11817 11817]

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 superblock lock for a soon died page.

*Severity: minor

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11706 11706]

Description: service threads may hog cpus when there are a lot of requests

Details: Insert cond_resched to give other threads a chance to use some CPU

*Severity: minor

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12747 12747]

Description: fix mal-formatted messages

Details: fix some mal-formatted DEBUG_REQ and LCONSOLE_ERROR_MSG messages

*Severity: minor

Frequency: always in liblustre

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11737 11737]

Description: wrong IS_ERR implementation in liblustre.h

Details: fix IS_ERR implementation in liblustre.h for right detect errors.

*Severity: minor

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10419 10419]

Description: Correct condition for output debug message.

Details: inode i_nlink equal zero is not enough for output message about disk corruption, i_ctime and i_mode should be also checked.

*Severity: minor

Frequency: always in patchless client

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12415 12415]

Description: add configure check for truncate_complete_page

Details: improve checks for exported symbols. This allow run check without
sources, but with Module.symvers shipped with kernel distribution. add check for truncate_complete_page used by patchless client.

*Severity: minor

Frequency: only run on patchless client.

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12858 12858]

Description: use do_facet on sanity.sh for test handling recoverables errors

Details: use do_facet instead of direct use sysctl for set fail_loc on OST

*Severity: minor

Frequency: only at startup

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11778 11778]

Description: Delay client connections to MDT until fist MDT->OST connect

Details: If a client tried to create a new file before the MDT had connected to any OSTs, the create would return EIO. Now the client will simply block until the MDT connects to the first OST and the create can succeed.

*Severity: minor

Frequency: at statup only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12860 12860]

Description: mds_lov_synchronize race leads to various problems

Details: simultaneous MDT->OST connections at startup can cause the sync to abort, leaving the OSC in a bad state.

=Changes from v1.6.0 to v1.6.0.1=

*Severity: normal

Frequency: on some architectures

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12404 12404]

Description: 1.6 client sometimes fails to mount from a 1.4 MDT

Details: Uninitialized flags sometimes cause configuration commands to be skipped.

*Severity: normal

Frequency: patchless clients only

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12391 12391]

Description: missing __iget() symbol export

Details: The __iget() symbol export is missing. To avoid the need for this on patchless clients the deathrow inode reaper is turned off, and we depend on the VM to clean up old inodes. This dependency was during via the fix for bug 12181.

*Severity: normal

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12848 12848]

Description: sanity.sh fail: test_52b

Details: The ll_inode_to_ext_flags() has a glitch which makes MDS return incorrect inode's flags to client.

=Changes from v1.4.10 to v1.6.0=

'''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 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.4.21-47.0.1.EL (RHEL 3), 2.6.5-7.283 (SLES 9), 2.6.9-42.0.10.EL (RHEL 4), 2.6.12.6 vanilla (kernel.org), 2.6.16.27-0.9 (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.8EL (RHEL 4)'''

'''Recommended e2fsprogs version: 1.39.cfs6'''

'''Note that reiserfs quotas are disabled on SLES 10 in this kernel'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=4900 4900]

Description: Async OSC create to avoid the blocking unnecessarily.

Details: If a OST has no remain object, system will block on the creating when need to create a new object on this OST. Now, ways use pre-created objects when available, instead of blocking on an empty osc while others are not empty. If we must block, we block for the shortest possible period of time.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=8007 8007]

Description: MountConf

Details: Lustre configuration is now managed via mkfs and mount commands instead of lmc and lconf. New obd types (MGS, MGC) are added for dynamic configuration management. See https://mail.clusterfs.com/wikis/lustre/MountConf for details.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=4482 4482]

Description: dynamic OST addition

Details: OSTs can now be added to a live filesystem

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9851 9851]

Description: startup order invariance

Details: MDTs and OSTs can be started in any order. Clients only require the MDT to complete startup.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=4899 4899]

Description: parallel, asynchronous orphan cleanup

Details: orphan cleanup is now performed in separate threads for each OST, allowing parallel non-blocking operation.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9862 9862]

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.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=4226 4226]

Description: Permanently set tunables

Details: All writable /proc/fs/lustre tunables can now be permanently set on a per-server basis, at mkfs time or on a live system.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10547 10547]

Description: Lustre message v2

Details: Add lustre message format v2.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9866 9866]

Description: client OST exclusion list

Details: Clients can be started with a list of OSTs that should be declared "inactive" for known non-responsive OSTs.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10088 10088]

Description: fine-grained SMP locking inside DLM

Details: Improve DLM performance on SMP systems by removing the single per-namespace lock and replace it with per-resource locks.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9332 9332]

Description: don't hold multiple extent locks at one time

Details: To avoid client eviction during large writes, locks are not held on multiple stripes at one time or for very large writes. Otherwise, clients can block waiting for a lock on a failed OST while holding locks on other OSTs and be evicted.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9293 9293]

Description: Multiple MD RPCs in flight.

Details: Further unserialise some read-only MDT RPCs - learn about intents. To avoid overly-overloading MDT, introduce a limit on number of MDT RPCs in flight for a single client and add /proc controls to adjust this limit.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=22484 22484]

Description: client read/write statistics

Details: Add client read/write call usage stats for performance 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.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=22485 22485]

Description: per-client statistics on server

Details: Add ldlm and operations statistics for each client in /proc/fs/lustre/mds|obdfilter/*/exports/

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=22486 22486]

Description: improved MDT statistics

Details: Add detailed MDT operations statistics in /proc/fs/lustre/mds/*/stats

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10968 10968]

Description: VFS operations stats

Details: Add client VFS call stats, trackable by pid, ppid, or gid /proc/fs/lustre/llite/*/stats_track_[pid|ppid|gid]

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=2258 2258]

Description: Dynamic service threads

Details: Within a small range, start extra service threads automatically when the request queue builds up.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11229 11229]

Description: Easy OST removal

Details: OSTs can be permanently deactivated with e.g. 'lctl conf_param lustre-OST0001.osc.active=0'

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11335 11335]

Description: MGS proc entries

Details: Added basic proc entries for the MGS showing what filesystems are served.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10998 10998]

Description: provide MGS failover

Details: Added config lock reacquisition after MGS server failover.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11461 11461]

Description: add Linux 2.4 support

Details: Added support for RHEL 2.4.21 kernel for 1.6 servers and clients

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10902 10902]

Description: plain/inodebits lock performance improvement

Details: Grouping plain/inodebits in granted list by their request modes and bits policy, thus improving the performance of search through the granted list.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11667 11667]

Description: Add "/proc/sys/lustre/debug_peer_on_timeout"

Details: 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: [https://bugzilla.lustre.org/show_bug.cgi?id=11264 11264]

Description: Add uninit_groups feature to ldiskfs2 to speed up e2fsck

Details: The uninit_groups feature works in conjunction with the kernel filesystem code (ldiskfs2 only) and e2fsprogs-1.39-cfs6 to speed up the pass1 processing of e2fsck. This is a read-only feature in ldiskfs2 only, so older kernels and current ldiskfs cannot mount filesystems that have had this feature enabled.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10816 10816]

Description: Improve multi-block allocation algorithm to avoid fragmentation

Details: The mballoc3 code (ldiskfs2 only) adds new mechanisms to improve allocation locality and avoid filesystem fragmentation.

*Severity: major

Frequency: mixed-endian client/server environments

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11214 11214]

Description: mixed-endian crashes

Details: The new msg_v2 system had some failures in mixed-endian environments.

*Severity: major

Frequency: when an incorrect nid is specified during startup

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10734 10734]

Description: ptlrpc connect to non-existant node causes kernel crash

Details: LNET can't be re-entered from an event callback, which happened when we expire a message after the export has been cleaned up. Instead, hand the zombie cleanup off to another thread.

*Severity: major

Frequency: only if OST filesystem is corrupted

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=9829 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: major

Frequency: liblustre (e.g. catamount) on a large cluster with >= 8 OSTs/OSS

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11684 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: major

Frequency: only for devices with external journals

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10719 10719]

Description: Set external device read-only also

Details: During a commanded failover stop, we set the disk device read-only while the server shuts down. We now also set any external journal device read-only at the same time.

*Severity: major

Frequency: when setting specific ost indicies

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11149 11149]

Description: QOS code breaks on skipped indicies

Details: Add checks for missing OST indicies in the QOS code, so OSTs created with --index need not be sequential.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12123 12123]

Description: ENOENT returned for valid filehandle during dbench.

Details: Check if a directory has children when invalidating dentries associated with an inode during lock cancellation. This fixes an incorrect ENOENT sometimes seen for valid filehandles during testing with dbench.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11330 11330]

Description: a large application tries to do I/O to the same resource and dies in the middle of it.

Details: Check the req->rq_arrival time after the call to ost_brw_lock_get(), but before we do anything about processing it & sending the BULK transfer request. This should help move old stale pending locks off the queue as quickly as obd_timeout.

*Severity: minor

Frequency: SFS test only (otherwise harmless)

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=6062 6062]

Description: SPEC SFS validation failure on NFS v2 over lustre.

Details: Changes the blocksize for regular files to be 2x RPC size, and not depend on stripe size.

*Severity: minor

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=6380 6380]

Description: Fix client-side osc byte counters

Details: The osc read/write byte counters in /proc/fs/lustre/osc/*/stats are now working

*Severity: minor

Frequency: always as root on SLES

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10667 10667]

Description: Failure of copying files with lustre special EAs.

Details: Client side always return success for setxattr call for lustre special xattr (currently only "trusted.lov").

*Severity: minor

Frequency: always

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10345 10345]

Description: Refcount LNET uuids

Details: The global LNET uuid list grew linearly with every startup; refcount repeated list entries instead of always adding to the list.

*Severity: minor

Frequency: only for kernels with patches from Lustre below 1.4.3

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11248 11248]

Description: Remove old rdonly API

Details: Remove old rdonly API which unused from at least lustre 1.4.3

*Severity: minor

Frequency: when upgrading from 1.4 while trying to change parameters

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11692 11692]

Description: The wrong (new) MDC name was used when setting parameters for upgraded MDT's. Also allows changing of OSC (and MDC) parameters if --writeconf is specified at tunefs upgrade time.

=Changes from v1.6.0 to v1.4.11=

'''Support for networks: socklnd - kernels up to 2.6.16, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1 viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12014 12014]

Description: ASSERTION failures when upgrading to the patchless zero-copy socklnd

Details: This bug affects "rolling upgrades", causing an inconsistent protocol version negotiation and subsequent assertion failure during rolling upgrades after the first wave of upgrades.

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10916 10916]

Description: added LNET self test

Details: landing b_self_test

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12316 12316]

Description: Add OFED1.2 support to o2iblnd

Details: o2iblnd depends on OFED's modules, if out-tree OFED's modules are installed (other than kernel's in-tree infiniband), there could be some problem while insmod o2iblnd (mismatch CRC of ib_* symbols). If extra Module.symvers is supported in kernel (i.e, 2.6.17), this link provides solution: https://bugs.openfabrics.org/show_bug.cgi?id=355 if extra Module.symvers is not supported in kernel, we will have to run the script in bug 12316 to update $LINUX/module.symvers before building o2iblnd. More details about this are in bug 12316.

*Severity: normal

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11680 11680]

Description: make panic on lbug configurable

*Severity: minor

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=13288 13288]

Description: Initialize cpumask before use

*Severity: minor

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11223 11223]

Details: Change "dropped message" CERRORs to D_NETERROR so they are logged instead of creating "console chatter" when a lustre timeout races with normal RPC completion.

*Severity: minor

Details: lnet_clear_peer_table can wait forever if user forgets to clear a lazy portal.

*Severity: minor

Details: libcfs_id2str should check pid against LNET_PID_ANY.

*Severity: minor

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12227 12227]

Description: cfs_duration_{u,n}sec() wrongly calculate nanosecond part of struct timeval.

Details: do_div() macro is used incorrectly.

=Changes from v1.4.9 to v1.6.0=

'''Support for networks: socklnd - kernels up to 2.6.16, qswlnd - Qsnet kernel modules 5.20 and later, openiblnd - IbGold 1.8.2, o2iblnd - OFED 1.1, viblnd - Voltaire ibhost 3.4.5 and later, ciblnd - Topspin 3.2.0, iiblnd - Infiniserv 3.3 + PathBits patch, gmlnd - GM 2.1.22 and later, mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x'''

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=10316 10316]

Description: Fixed console chatter in case of -ETIMEDOUT.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11684 11684]

Description: Added D_NETTRACE for recording network packet history (initially only for ptllnd). Also a separate userspace ptllnd facility to gather history which should really be covered by D_NETTRACE too, if only CDEBUG recorded history in userspace.

*Severity: enhancement

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11094 11094]

Description: Multiple instances for o2iblnd

Details: Allow multiple instances of o2iblnd to enable networking over multiple HCAs and routing between them.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12458 12458]

Description: Assertion failure in kernel ptllnd caused by posting passive bulk buffers before connection establishment complete.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12455 12455]

Description: A race in kernel ptllnd between deleting a peer and posting new communications for it could hang communications - manifesting as "Unexpectedly long timeout" messages.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12432 12432]

Description: Kernel ptllnd lock ordering issue could hang a node.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12016 12016]

Description: node crash on socket teardown race

*Severity: major

Frequency: after Ptllnd timeouts and portals congestion

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11659 11659]

Description: Credit overflows

Details: This was a bug in ptllnd connection establishment. The fix implements better peer stamps to disambiguate connection establishment and ensure both peers enter the credit flow state machine consistently.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11394 11394]

Description: kptllnd didn't propagate some network errors up to LNET

Details: This bug was spotted while investigating 11394. The fix ensures network errors on sends and bulk transfers are propagated to LNET/lustre correctly.

*Severity: major

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11616 11616]

Description: o2iblnd handle early RDMA_CM_EVENT_DISCONNECTED.

Details: If the fabric is lossy, an RDMA_CM_EVENT_DISCONNECTED callback can occur before a connection has actually been established. This caused an assertion failure previously.

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11201 11201]

Description: lnet deadlock in router_checker

Details: turned ksnd_connd_lock, ksnd_reaper_lock, and ksock_net_t:ksnd_lock into BH locks to eliminate potential deadlock caused by ksocknal_data_ready() preempting code holding these locks.

*Severity: major

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11126 11126]

Description: Millions of failed socklnd connection attempts cause a very slow FS

Details: added a new route flag ksnr_scheduled to distinguish from ksnr_connecting, so that a peer connection request is only turned down for race concerns when an active connection to the same peer is under progress (instead of just being scheduled).

*Severity: normal

Frequency: rare

Description: gmlnd ignored some transmit errors when finalizing lnet messages.

*Severity: normal

Frequency: rare

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=11472 11472]

Description: Changed the default kqswlnd ntxmsg=512

*Severity: minor

Frequency: rare

Description: Ptllnd didn't init kptllnd_data.kptl_idle_txs before it could be possibly accessed in kptllnd_shutdown. Ptllnd should init kptllnd_data.kptl_ptlid2str_lock before calling kptllnd_ptlid2str.

*Severity: minor

Frequency: rare

Description: ptllnd logs a piece of incorrect debug info in kptllnd_peer_handle_hello.

*Severity: minor

Frequency: rare

Description: the_lnet.ln_finalizing was not set when the current thread is about to complete messages. It only affects multi-threaded user space LNet.

*Severity: minor

Frequency: 'lctl peer_list' issued on a mx net

Bugzilla: [https://bugzilla.lustre.org/show_bug.cgi?id=12237 12237]

Description: Enable lctl's peer_list for MXLND

=[http://wiki.lustre.org/index.php?title=Change_Log_1.4 Change logs for 1.4.x releases]=

2008-01-28T03:31:49Z

Lollsolo: /* Synopsys */

== CFS ==

* [http://wiki.lustre.org/images/a/a3/Gelato-2004-05.pdf '''Lustre state and production installations''']
** Presentation on gelato.org meeting
** May 2004

* [http://wiki.lustre.org/images/e/ea/Lustre-usg-2003.pdf '''Lustre File System ''']
** A presentation on the state of Lustre in mid-2003 and the path towards Lustre1.0.
** Summer, 2003

* [http://wiki.lustre.org/images/d/d2/Ols2003.pdf '''Lustre: Building a cluster file system for 1,000 node clusters''']
** A technical presentation about our successes and mistakes during 2002-2003.
** Summer 2003

* [http://wiki.lustre.org/images/6/6f/T10-062002.pdf '''Lustre: Scalable Clustered Object Storage''']
** A technical presentation on Lustre.
** June,2002

* [http://wiki.lustre.org/images/b/b5/001_lustretechnical-fall2002.pdf '''Lustre - the inter-galactic cluster file system?''']
** A technical overview of Lustre from 2002.
** June,2002

* [http://wiki.lustre.org/images/7/79/Intragalactic-2001.pdf '''Lustre Light: a simpler fully functional cluster file system''']
** September, 2001

* [http://wiki.lustre.org/images/c/c9/LustreSystemAnatomy.pdf '''Lustre System Anatomy''']
** Lustre component overview.

* [http://wiki.lustre.org/images/a/af/Intergalactic-062001.pdf '''Lustre: the intergalactic file system for the international labs?''']
** Presentation for Linux World and elsewhere on Lustre and Next Generation Data Centers
** June,2001

* [http://wiki.lustre.org/images/4/44/Obdcluster.pdf '''The object based storage cluster file systems and parallel I/O''']
** Sandia presentation on Lustre and Linux clustering

* [http://wiki.lustre.org/images/a/a2/Sdi-clusters.pdf '''Linux clustering and storage management''']
** Powerpoint slides of an overview of cluster and OBD technology

* [http://wiki.lustre.org/images/8/81/Lustre-sow-dist.pdf '''Lustre Technical Project Summary''']
** A Lustre roadmap presented to address the [http://wiki.lustre.org/images/7/70/SGSRFP.pdf Tri-Labs/DOD SGS File System RFP].
** July 2001

* [http://wiki.lustre.org/images/b/bd/Dfsprotocols.pdf '''File Systems for Clusters from a Protocol Perspective''']
** A comparative description of several distributed file systems.
** Proc. Second Extreme Linux Topics Workshop, Monterey CA, Jun. 1999.

* [http://www.pdl.cs.cmu.edu/NASD '''CMU NASD project''']

* [http://wiki.lustre.org/images/2/24/Osd-r03.pdf '''Working draft T10 OSD''']
** A standards effort exists in the T10 OSD working group proposal.
** October 2000

== Cray User Group ==

* '''Guidelines for Efficient Parallel I/O on the Cray XT3/XT4 '''
** Jeff Larkin, Mark Fahey, proceedings of CUG2007
** [http://wiki.lustre.org/images/3/3f/Larkin_paper.pdf Paper in PDF format]

* '''XT7? Integrating and Operating a Conjoined XT3+XT4 System'''
** [http://wiki.lustre.org/images/b/b9/Canon_slides.pdf Presentation:] Presented by ORNL on CUG 2007
** [http://wiki.lustre.org/images/f/fa/Canon_paper.pdf Paper:]This paper describes the processes and tools used to move production work from the pre-existing XT3 to the new system incorporating that same XT3, including novel application of Lustre routing capabilities.

* '''Using IOR to Analyze the I/O Performance'''
** Presented by Hongzhang Shan,John Shalf (NERSC) on CUG 2007
**[http://wiki.lustre.org/images/e/ef/Using_IOR_to_Analyze_IO_Performance.pdf Slides in PDF format]

* '''A Center-Wide File System using Lustre'''
** Shane Canon, H.Sharp Oral, proceedings of CUG2006
** [http://wiki.lustre.org/images/7/77/A_Center-Wide_FS_using_Lustre.pdf Paper in PDF format]

== HEPiX Talks ==
* [https://indico.desy.de/conferenceTimeTable.py?confId=257&showDate=all&showSession=all&detailLevel=contribution&viewMode=plain Spring HEPiX 2007]: April 23-27, 2007
* '''Storage Evaluations at BNL'''
** Presented by Robert Petkus - BNL
** Performance comparison between ZFS, XFS and EXT3 on a Sun Thumper
** [http://wiki.lustre.org/images/d/da/Storage_Evaluations%40BNL.pdf Slides in PDF format]
** Slides on HPPix site: [https://indico.desy.de/getFile.py/access?contribId=26&sessionId=40&resId=1&materialId=slides&confId=257 Storage Evaluations at BNL]

* '''Lustre Experience at CEA/DIF'''
** Presented by J-Ch Lafoucriere
** [http://wiki.lustre.org/images/5/58/DIF.pdf Slides in PDF format]
** Slides on HEPix site: [https://indico.desy.de/getFile.py/access?contribId=44&sessionId=39&resId=0&materialId=slides&confId=257 Lustre Experience at CEA/DIF]

== Indiana University ==
* '''Wide Area Filesystem Performance using Lustre on the TeraGrid'''
** TeraGrid 2007 conference, June 2007
** [http://wiki.lustre.org/images/2/20/Lustre_wan_tg07.pdf Paper in PDF format]

== Karlsruhe Lustre Talks ==

* http://www.rz.uni-karlsruhe.de/dienste/lustretalks.php
* '''Filesystems on SSCK's HP XC6000'''
** Einführungsveranstaltung im Rechenzentrum (2005): [http://wiki.lustre.org/images/7/7c/Karlsruhe0503.pdf Karlsruhe0503.pdf]
* '''Experiences & Performance of SFS/Lustre Cluster File System in Production'''
** HP-CAST 4 in Krakau (10.5.2005): [http://wiki.lustre.org/images/9/95/Karlsruhe0510.pdf Karlsruhe0510.pdf]
* '''Experiences with HP SFS/Lustre in HPC Production'''
** ISC 2005 in Heidelberg (24.6.2005): [http://wiki.lustre.org/images/5/5f/Karlsruhe0506.pdf Karlsruhe0506.pdf]
* '''Experiences with 10 Months HP SFS/Lustre in HPC Production'''
** HP-CAST 5 in Seattle (11.11.2005): [http://wiki.lustre.org/images/1/17/Karlsruhe0511.pdf Karlsruhe0511.pdf]
* '''Performance Monitoring in a HP SFS Environment'''
** HP-CCN in Seattle (12.11.2005): [http://wiki.lustre.org/images/a/aa/Karlsruhe0512.pdf Karlsruhe0512.pdf]
* '''Experiences with HP SFS/Lustre at SSCK'''
** SGPFS 5 in Stuttgart (4.4.2006): [http://wiki.lustre.org/images/0/0b/Karlsruhe0604.pdf Karlsruhe0604.pdf]

== Ohio State University ==

* '''Benefits of High Speed Interconnects to Cluster File Systems: A Case Study with Lustre'''
** Parallel and Distributed Processing Symposium, 2006. IPDPS 2006.
** Lustre performance comparison when using InfiniBand and Quadrics interconnects
** [http://wiki.lustre.org/images/d/d8/Cac06_lustre.pdf Paper in PDf format]
** [http://nowlab.cse.ohio-state.edu/publications/conf-papers/2006/yu-cac06.pdf Download paper at OSU site]

== ORNL ==

* '''Exploiting Lustre File Joining for Effective Collective IO'''
** [http://wiki.lustre.org/images/d/db/Yu_lustre.pdf Paper in pdf format]
** Proceedings of the CCGrid'07, May 2007.

== SUN ==
* '''Tokyo Tech Tsubame Grid Storage Implementation'''
** By Syuuichi Ihara, May,2007
** [http://wiki.lustre.org/images/7/79/Thumper-BP-6.pdf Paper in pdf format]
** [http://www.sun.com/blueprints/0507/820-2187.html Sun BluePrints Publications]

== Synopsys ==

=== Optimizing Storage and I/O For Distributed Processing On Enterprise & High Performance Compute(HPC)Systems For Mask Data Preparation Software (CATS)===

* Glenn Newell, Sr.IT Solutions Mgr,

* Naji Bekhazi,Director Of R&D,Mask Data Prep (CATS)

* Ray Morgan,Sr.Product Marketing Manager,Mask Data Prep(CATS)

* 2007

http://wiki.lustre.org/index.php?title=Image:Hpc_cats_wp.pdf

== University of Colorado, Boulder ==
* '''Shared Parallel Filesystem in Heterogeneous Linux Multi-Cluster Environment'''
** [http://wiki.lustre.org/images/8/81/LciPaper.pdf Paper in PDF format]
** proceedings of the 6th LCI International Conference on Linux Clusters: The HPC Revolution.(2005)
** The management issues mentioned in the last part of this paper have been addressed
** [http://linuxclustersinstitute.org/Linux-HPC-Revolution/Archive/PDF05/17-Oberg_M.pdf Paper at CU site](It's the same as the attachment of LCI paper above.)

== University of Minnesota ==
* '''Coordinating Parallel Hierarchical Storage Management in Object-base Cluster File Systems'''
** MSST2006, Conference on Mass Storage Systems and Technologies(May 2006)
**[http://wiki.lustre.org/images/f/fc/MSST-2006-paper.pdf Paper in PDF format]

File:Hpc cats wp.pdf

2008-01-28T03:30:53Z

Lollsolo: