[Ocfs2-users] ERROR: __ocfs2_find_path: Owner 2009289 has bad blkno in extent list at depth 1

[Eugene Istomin]

Hello,

we have a problems in production hypervisor (kernel 3.12.26-5-xen) - 
after reflinking some VMs & starting them  in new location i'm geeting :

[2867722.577610] OCFS2: ERROR (device sdb1): __ocfs2_find_path: Owner 2009289 has bad blkno in extent list at depth 1 (index 234)

[2867722.577682] File system is now read-only due to the potential of on-disk corruption. Please run fsck.ocfs2 once the file system is unmounted.
[2867722.577735] (qemu-system-i38,28195,3):__ocfs2_rotate_tree_left:2957 ERROR: status = -30
[2867722.577767] (qemu-system-i38,28195,3):ocfs2_rotate_tree_left:3232 ERROR: status = -30
[2867722.577795] (qemu-system-i38,28195,3):ocfs2_try_to_merge_extent:3781 ERROR: status = -30
[2867722.609382] OCFS2: ERROR (device sdb1): __ocfs2_find_path: Owner 2009289 has bad blkno in extent list at depth 1 (index 234)

[2867722.609479] (qemu-system-i38,28180,3):__ocfs2_rotate_tree_left:2957 ERROR: status = -30
[2867722.609541] (qemu-system-i38,28180,3):ocfs2_rotate_tree_left:3244 ERROR: status = -30
[2867722.609594] (qemu-system-i38,28180,3):ocfs2_try_to_merge_extent:3781 ERROR: status = -30
[2867722.638580] OCFS2: ERROR (device sdb1): __ocfs2_find_path: Owner 2009289 has bad blkno in extent list at depth 1 (index 234)

[2867722.638639] (qemu-system-i38,28190,1):__ocfs2_rotate_tree_left:2957 ERROR: status = -30
[2867722.638669] (qemu-system-i38,28190,1):ocfs2_rotate_tree_left:3244 ERROR: status = -30
[2867722.638699] (qemu-system-i38,28190,1):ocfs2_try_to_merge_extent:3781 ERROR: status = -30





##fsck.ocfs2 -f /dev/disk/by-label/storage 
fsck.ocfs2 1.8.2
Checking OCFS2 filesystem in /dev/disk/by-label/storage:
  Label:              storage
  UUID:               313C9C349D9B430FBAA3C3C7989F4CA3
  Number of blocks:   558344960
  Block size:         4096
  Number of clusters: 4362070
  Cluster size:       524288
  Number of slots:    10

/dev/disk/by-label/storage was run with -f, check forced.
Pass 0a: Checking cluster allocation chains
Pass 0b: Checking inode allocation chains
Pass 0c: Checking extent block allocation chains
Pass 1: Checking inodes and blocks
[EXTENT_LIST_FREE] Extent list in owner 2009289 claims 235 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? <y> y
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> y
fsck.ocfs2: refcount.c:446: refcount_extent_insert: Assertion `0' failed.
Aborted


ok, try to say "no"


#fsck.ocfs2 -f /dev/disk/by-label/storage 
fsck.ocfs2 1.8.2
Checking OCFS2 filesystem in /dev/disk/by-label/storage:
  Label:              storage
  UUID:               313C9C349D9B430FBAA3C3C7989F4CA3
  Number of blocks:   558344960
  Block size:         4096
  Number of clusters: 4362070
  Cluster size:       524288
  Number of slots:    10

/dev/disk/by-label/storage was run with -f, check forced.
Pass 0a: Checking cluster allocation chains
Pass 0b: Checking inode allocation chains
Pass 0c: Checking extent block allocation chains
Pass 1: Checking inodes and blocks
[EXTENT_LIST_FREE] Extent list in owner 2009289 claims 235 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? <y> y
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> n
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> n
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> n
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> n
[EXTENT_BLKNO_RANGE] Extent record 0 in owner 2009289 refers to a block that is out of range.  Remove this record from the extent list? <y> n
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 0 instead of 284502. Fix? <y> n
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284502 instead of 284504. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284503 instead of 284505. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284504 instead of 284506. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284505 instead of 284507. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284506 instead of 284508. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284517 instead of 284519. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284518 instead of 284520. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284519 instead of 284521. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284520 instead of 284522. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284529 instead of 284531. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284530 instead of 284532. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284531 instead of 284533. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284532 instead of 284534. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284533 instead of 284535. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284534 instead of 284536. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284535 instead of 284537. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284536 instead of 284538. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284547 instead of 284549. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284548 instead of 284550. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284549 instead of 284551. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284550 instead of 284552. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284551 instead of 284553. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284552 instead of 284554. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284561 instead of 284563. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284562 instead of 284564. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284563 instead of 284565. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284564 instead of 284566. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284567 instead of 284569. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284568 instead of 284570. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284581 instead of 284583. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284582 instead of 284584. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284585 instead of 284587. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284586 instead of 284588. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284593 instead of 284595. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284594 instead of 284596. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284595 instead of 284597. Fix? <y> y
[EXTENT_OVERLAP] Extent record of owner 2009289 is incorrectly set to 284596 instead of 284598. Fix? <y> y



Please help in problem resolving.
---
Best regards,
Eugene Istomin