Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Lustre 2.7.0
-
[root@panda-oss-25-4 ~]# uname -a
Linux panda-oss-25-4.sdsc.edu 3.10.73-1.el6.elrepo.x86_64 #1 SMP Thu Mar 26 16:28:30 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@panda-oss-25-4 ~]# rpm -aq | grep lustre
lustre-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-osd-zfs-mount-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-iokit-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-source-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-osd-zfs-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-modules-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
lustre-tests-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
[ root@panda-oss-25-4 ~]# uname -a Linux panda-oss-25-4.sdsc.edu 3.10.73-1.el6.elrepo.x86_64 #1 SMP Thu Mar 26 16:28:30 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux [ root@panda-oss-25-4 ~]# rpm -aq | grep lustre lustre-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-osd-zfs-mount-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-iokit-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-source-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-osd-zfs-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-modules-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64 lustre-tests-2.7.51-3.10.73_1.el6.elrepo.x86_64_gb019b03.x86_64
-
4
-
9223372036854775807
Description
No sign or indication, ie lustre-log or error messages, OSS unexpectantly crash (please see console image).
/var/log/messages is attached
Attachments
Activity
Link | New: This issue is duplicated by AEON-11 [ AEON-11 ] |
Link | New: This issue is duplicated by EDU-28 [ EDU-28 ] |
Link | Original: This issue is related to LDEV-142 [ LDEV-142 ] |
Link | New: This issue is related to LDEV-143 [ LDEV-143 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Assignee | Original: Zhenyu Xu [ bobijam ] | New: Mikhail Pershin [ tappro ] |
Fix landed for 2.8. We'll reopen if this issue still is hit on Hyperion. If there is still an issue at SDSC and it is not, as hoped, a duplicate of this issue then please open a new ticket to track that issue.