Anybody have any idea what this error involves? Or how to resolve it? Oct 30 05:11:24 groupwise-1-mht kernel: (8494,0):ocfs2_extent_map_find_leaf:287 ERROR: status = -53 Oct 30 05:11:24 groupwise-1-mht kernel: OCFS2: ERROR (device dm-0): ocfs2_extent_map_find_leaf: Extent 29 at e_blkno 1973744 of inode 6518860 goes past ip_clusters of 441 Oct 30 05:11:24 groupwise-1-mht kernel: Oct 30 05:11:24 groupwise-1-mht kernel: File system is now read-only due to the potential of on-disk corruption. Please run fsck.ocfs2 once the file system is unmounted. Oct 30 05:11:24 groupwise-1-mht kernel: (8494,0):ocfs2_extent_map_lookup_read:383 ERROR: status = -53 Oct 30 05:11:24 groupwise-1-mht kernel: (8494,0):ocfs2_extent_map_get_blocks:858 ERROR: status = -53 Oct 30 05:11:24 groupwise-1-mht kernel: (8494,0):ocfs2_get_block:171 ERROR: Error -53 from get_blocks(0xf3c2d608, 0, 1, 0, NULL) - Andy Andy Kipp Network Administrator Velcro USA Inc. 406 Brown Ave. Manchester, NH 03103 Phone: (603) 222-4844 Email: akipp@velcro.com CONFIDENTIALITY NOTICE: This email is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please so advise immediately.
Which version of OCFS2? Did you run fsck.ocfs2 -f on that device? Do: # echo stat <6518860> | debugfs.ocfs2 -n /dev/sdX >/tmp/ext.out Email ext.out. Andy Kipp wrote:> Anybody have any idea what this error involves? Or how to resolve it? > > > Oct 30 05:11:24 groupwise-1-mht kernel: > (8494,0):ocfs2_extent_map_find_leaf:287 ERROR: status = -53 > Oct 30 05:11:24 groupwise-1-mht kernel: OCFS2: ERROR (device dm-0): > ocfs2_extent_map_find_leaf: Extent 29 at e_blkno 1973744 of inode > 6518860 goes past ip_clusters of 441 > Oct 30 05:11:24 groupwise-1-mht kernel: > Oct 30 05:11:24 groupwise-1-mht kernel: File system is now read-only > due to the potential of on-disk corruption. Please run fsck.ocfs2 once > the file system is unmounted. > Oct 30 05:11:24 groupwise-1-mht kernel: > (8494,0):ocfs2_extent_map_lookup_read:383 ERROR: status = -53 > Oct 30 05:11:24 groupwise-1-mht kernel: > (8494,0):ocfs2_extent_map_get_blocks:858 ERROR: status = -53 > Oct 30 05:11:24 groupwise-1-mht kernel: (8494,0):ocfs2_get_block:171 > ERROR: Error -53 from get_blocks(0xf3c2d608, 0, 1, 0, NULL) > > - Andy > > > Andy Kipp > Network Administrator > Velcro USA Inc. > 406 Brown Ave. > Manchester, NH 03103 > Phone: (603) 222-4844 > Email: akipp@velcro.com > > CONFIDENTIALITY NOTICE: > This email is intended only for the person or entity to which it is > addressed and may contain confidential and/or privileged material. Any > unauthorized review, use, disclosure or distribution is prohibited. If > you are not the intended recipient, please contact the sender by reply > e-mail and destroy all copies of the original message. If you are the > intended recipient but do not wish to receive communications through > this medium, please so advise immediately. > > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users >
> Which version of OCFS2?ocfs2 1.2.1 (sles) ocfs2-tools 1.2.1 (sles)> Did you run fsck.ocfs2 - f on that device?Not yet. Wanted to see what the error was about. Before I take down a production machine to do the fsck.>Do: > # echo stat <6518860> | debugfs.ocfs2 - n /dev/sdX >/tmp/ext.out > Email ext.out.This keeps returning saying that the device can not be found. I have tried running it with the following options with consideration for multipathing: /dev/sdb /dev/sdd /dev/dm-0 /dev/disk/by-name/vol_groupwise_data Am I missing the obvious? Thank for your help. Andy Kipp Network Administrator Velcro USA Inc. 406 Brown Ave. Manchester, NH 03103 Phone: (603) 222-4844 Email: akipp@velcro.com CONFIDENTIALITY NOTICE: This email is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please so advise immediately.
Replace sdX with the device on which the ocfs2 fs exists. You can use "mount | grep ocfs2" to find that volume. If the inode on disk is good, one explanation for the issue could be the lvb bug which was fixed in 1.2.2. Ping Novell to get a PTF kernel with ocfs2 1.2.3. Andy Kipp wrote:> > Which version of OCFS2? > > ocfs2 1.2.1 (sles) > ocfs2-tools 1.2.1 (sles) > > >> Did you run fsck.ocfs2 - f on that device? >> > > Not yet. Wanted to see what the error was about. Before I take down a > production machine to do the fsck. > > >> Do: >> # echo stat <6518860> | debugfs.ocfs2 - n /dev/sdX >/tmp/ext.out >> Email ext.out. >> > > This keeps returning saying that the device can not be found. I have > tried running it with the following options with consideration for > multipathing: > /dev/sdb > /dev/sdd > /dev/dm-0 > /dev/disk/by-name/vol_groupwise_data > > Am I missing the obvious? > Thank for your help. > > > Andy Kipp > Network Administrator > Velcro USA Inc. > 406 Brown Ave. > Manchester, NH 03103 > Phone: (603) 222-4844 > Email: akipp@velcro.com > > CONFIDENTIALITY NOTICE: > This email is intended only for the person or entity to which it is > addressed and may contain confidential and/or privileged material. Any > unauthorized review, use, disclosure or distribution is prohibited. If > you are not the intended recipient, please contact the sender by reply > e-mail and destroy all copies of the original message. If you are the > intended recipient but do not wish to receive communications through > this medium, please so advise immediately. > >