https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1292 Lustre <p>We have a lustre 2.1 filesystem with 2mds and 4oss, each has two osts. There is an issue recently, one ost reports a ldiskfs_ext_walk_space error, then remount with read-only. We reboot the oss, the ost can mount and work without any fsck. Below is the syslog:</p> <p>Apr 8 21:00:43 oss1 kernel: LDISKFS-fs error (device sdb): ldiskfs_ext_walk_space: inode #12388311: (comm ll_ost_io_153) path<span class="error">&#91;1&#93;</span>.p_hdr == NULL<br/> Apr 8 21:00:43 oss1 kernel: Aborting journal on device sdb-8.<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 7722:0:(obd.h:1613:obd_transno_commit_cb()) dcfs-OST0007: transno 3231335624 commit error: 2<br/> Apr 8 21:00:43 oss1 kernel: LDISKFS-fs error (device sdb): ldiskfs_journal_start_sb: Detected aborted journal<br/> Apr 8 21:00:43 oss1 kernel: LDISKFS-fs (sdb): Remounting filesystem read-only<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 31323:0:(fsfilt-ldiskfs.c:492:fsfilt_ldiskfs_brw_start()) can't get handle for 45 credits: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 31323:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LDISKFS-fs (sdb): Remounting filesystem read-only<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18874:0:(fsfilt-ldiskfs.c:358:fsfilt_ldiskfs_start()) error starting handle for op 8 (71 credits): rc -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(fsfilt-ldiskfs.c:492:fsfilt_ldiskfs_brw_start()) can't get handle for 569 credits: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(fsfilt-ldiskfs.c:358:fsfilt_ldiskfs_start()) error starting handle for op 8 (71 credits): rc -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(fsfilt-ldiskfs.c:358:fsfilt_ldiskfs_start()) Skipped 2 previous similar messages<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18035:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 8014:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30<br/> Apr 8 21:00:43 oss1 kernel: LustreError: 18033:0:(filter_io_26.c:712:filter_commitrw_write()) error starting transaction: rc = -30</p> rhel5.6/kernel 2.6.18-238.19.1.el5, intel xeon x5650 LU-1292

ldiskfs_ext_walk_space error

Bug Major Resolved Cannot Reproduce WC Triage Larry Gu Sun, 8 Apr 2012 11:44:09 +0000 Wed, 6 Nov 2013 17:25:05 +0000 Wed, 6 Nov 2013 17:25:05 +0000 Lustre 2.1.0 0 2 <p>We used to have a similar problem, running 'forced' fsck on the failed OST did the trick, so you might give it a try.</p> Development Rank 1|hzv393: Rank (Obsolete) 4026 Severity