Hi,

I have a problem in Oracle VM 3.4.5 with an OCFS2 filesystem that should be mounted in 2 nodes. I got bad magic number error and I can't proceed to mount the filesystem which
our OCFS2 cluster, which I couldn't solve by myself.
In short, I have a OCFS2 cluster with 2 nodes and a shared storage LUN. I have mapped the LUN to all nodes cluster, formatted them as OCFS2 filesystems and mounted them successfully. The system has been running OK. Today, the first server crash and the filesystem become inaccessible.
the repository size is 4.6T ( more than 2T)
The error is below:

# fsck.ocfs2 /dev/mapper/3600a098000d722350000014c5b57fd85
fsck.ocfs2 1.8.6
fsck.ocfs2: Bad magic number in inode while initializing the DLM

# fsck.ocfs2 -r 2 /dev/mapper/3600a098000d722350000014c5b57fd85
fsck.ocfs2 1.8.6
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup block#1048576? <n> y
fsck.ocfs2: Bad magic number in inode while initializing the DLM

# fsck.ocfs2 -r 6 /dev/mapper/3600a098000d722350000014c5b57fd85
fsck.ocfs2 1.8.6
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup block#268435456? <n> y
fsck.ocfs2: Bad magic number in inode while initializing the DLM

#fsck.ocfs2 -n /dev/mapper/3600a098000d722350000014c5b57fd85
fsck.ocfs2 1.8.6
Checking OCFS2 filesystem in /dev/mapper/3600a098000d722350000014c5b57fd85:
Label: OVS3b0058584fb9e
UUID: 0004FB0000050000E823B0058584FB9E
Number of blocks: 1205862400
Block size: 4096
Number of clusters: 4710400
Cluster size: 1048576
Number of slots: 32

journal recovery: Bad magic number in inode while looking up the journal inode for slot 0
fsck encountered unrecoverable errors while replaying the journals and will not continue

Any one have idea ?