[lustre-discuss] zfs and luster 2.5.3.90

[Peter Kjellström]

On Fri, 15 Jan 2016 15:28:46 +0000
Frederick Lefebvre <frederick.lefebvre at calculquebec.ca> wrote:

FWIW, we at NSC run three sets of lustre+zfs in production currently:

2.5.3-5chaos + 0.6.4.1-1 + 2.6.32-504.16.2
2.5.3-something + 0.6.3-1.2 + 2.6.32-504.8.1.el6.nsc1
2.4.2-llnl13chaos + 0.6.3-1 + 2.6.32-431.20.3

> If you think you need a more recent version of ZFS, we have run Lustre
> 2.5.3 with ZFS up to 0.6.5.3 by building Lustre with patches from the
> following jiras:
...

If running 0.6.5.3 you might want to be aware that master has been
stepped back to 0.6.4:

Author: Jinshan Xiong <jinshan.xiong at intel.com>  2015-12-23 22:14:31
Committer: Oleg Drokin <oleg.drokin at intel.com>  2016-01-05 19:57:08
Parent: eb6cd4804d65dda1b6ea4a1289cc01647d03a47a (LU-7223 tests: print
more information when mmp.sh failed) Child:
08fcdbb95cd7ab3fc1246f03c3ef27c0b8a0d218 (LU-7084 obd: correct some OBD
allocator macro defines) Branches: remotes/origin/iu-sk,
remotes/origin/master Follows: 2.7.64, v2_7_64, v2_7_64_0 Precedes:
2.7.65, v2_7_65, v2_7_65_0

    LU-7404 zfs: reset ZFS baseline to 0.6.4.2
    
    ZFS 0.6.5.2 is known to introduce I/O problems with the following
    stack backtrace:
    
    Call Trace:
     [] ? vdev_mirror_child_done+0x0/0x30 [zfs]
     [] io_schedule+0x73/0xc0
     [] cv_wait_common+0xaf/0x130 [spl]
     [] ? autoremove_wake_function+0x0/0x40
...

/Peter K