[Ocfs2-users] Error when fsck.ocfs2

[Sunil Mushran]

So that's appears to be ok. How about a strace.

strace -o /tmp/fsck.out fsck.ocfs2 /dev/mapper/360...


On 04/08/2011 10:24 AM, Mauro Parra wrote:
> debugfs.ocfs2 -R "ls -l //" /dev/mapper/360a98000572d434e4e6f6335524b396f_part1
> 	514             drwxr-xr-x   6     0     0            4096 18-Feb-2011 14:03 .
> 	514             drwxr-xr-x   6     0     0            4096 18-Feb-2011 14:03 ..
> 	515             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 bad_blocks
> 	516             -rw-r--r--   1     0     0         2097152
> 18-Feb-2011 14:03 global_inode_alloc
> 	517             -rw-r--r--   1     0     0         1048576
> 18-Feb-2011 14:03 slot_map
> 	518             -rw-r--r--   1     0     0         1048576
> 18-Feb-2011 14:03 heartbeat
> 	519             -rw-r--r--   1     0     0    549761056768
> 18-Feb-2011 14:03 global_bitmap
> 	520             drwxr-xr-x   2     0     0            4096
> 14-Mar-2011 13:02 orphan_dir:0000
> 	521             drwxr-xr-x   2     0     0            4096
> 4-Apr-2011 16:15 orphan_dir:0001
> 	522             drwxr-xr-x   2     0     0            4096
> 18-Feb-2011 14:03 orphan_dir:0002
> 	523             drwxr-xr-x   2     0     0            4096
> 18-Feb-2011 14:03 orphan_dir:0003
> 	524             -rw-r--r--   1     0     0         4194304
> 18-Feb-2011 14:03 extent_alloc:0000
> 	525             -rw-r--r--   1     0     0         4194304
> 18-Feb-2011 14:03 extent_alloc:0001
> 	526             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 extent_alloc:0002
> 	527             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 extent_alloc:0003
> 	528             -rw-r--r--   1     0     0         4194304
> 18-Feb-2011 14:03 inode_alloc:0000
> 	529             -rw-r--r--   1     0     0         4194304
> 18-Feb-2011 14:03 inode_alloc:0001
> 	530             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 inode_alloc:0002
> 	531             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 inode_alloc:0003
> 	533             -rw-r--r--   1     0     0        33554432
> 18-Feb-2011 14:03 journal:0001
> 	534             -rw-r--r--   1     0     0        33554432
> 18-Feb-2011 14:03 journal:0002
> 	535             -rw-r--r--   1     0     0        33554432
> 18-Feb-2011 14:03 journal:0003
> 	537             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 local_alloc:0001
> 	538             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 local_alloc:0002
> 	539             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 local_alloc:0003
> 	540             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 truncate_log:0000
> 	541             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 truncate_log:0001
> 	542             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 truncate_log:0002
> 	543             -rw-r--r--   1     0     0               0
> 18-Feb-2011 14:03 truncate_log:0003
>
>
> On Fri, Apr 8, 2011 at 11:58 AM, Sunil Mushran<sunil.mushran at oracle.com>  wrote:
>> On 04/08/2011 09:25 AM, Mauro Parra wrote:
>>> Hello,
>>> I'm getting this error:
>>>
>>> $fsck.ocfs2  /dev/mapper/360a98000572d434e4e6f6335524b396f_part1
>>> fsck.ocfs2: File not found by ocfs2_lookup while locking down the cluster
>>>
>>> Any idea or hint?
>> This means it failed to lookup the journal in the system directory.
>>
>> What does the following show?
>> # debugfs.ocfs2 -R "ls -l //" /dev/mapper/...
>>
>>
>
>