[Ocfs2-users] JBD: no valid journal superblock found

[Sunil Mushran]

You may want all nodes to be on the same kernel version. 2.6.5-7.283.

But that's not the problem. There was a bug in tunefs.ocfs2 1.1.4. The
jbd superblock was not endian correct. Was fixed shortly thereafter.

You can fix this issue as follows:
1. Use yast to upgrade to ocfs2-tools 1.2.1 (or higher).

2. Use debugfs.ocfs2 to find the current size of the journals.
# echo "ls -l //" | debugfs.ocfs2 /dev/sdX
The format closely resembles ls -l.

3. Resize journals to say 1M more than the current size.
# tunefs.ocfs2 -J size=xM /dev/sdX

FYI, journal resize is an offline operation.

enohi ibekwe wrote:
> Hello,
>
> I am attempting to add a node (node 2) to an existing 2 node ( node 0 
> and node1) ocfs2 cluster.
> All nodes are running SLES9 and ocfs-tools-1.1.4-0.5, 
> ocfs-console-1.1.4-0.5. However the are not running identical kernels 
> ( node 0 and node 1 are 2.6.5-7.267-bigsmp i686 and node 2 is  
> 2.6.5-7.283-bigsmp) . They have installed the ocfs that ships with SLES9.
>
> When I attempt to mount the ocfs system on any of the nodes I get a 
> the error
> mount.ocfs2: Invalid argument while mounting /dev/sdb1 on 
> /u02/oradata/orcl
>
> and the dmesg error is
> JBD: no valid journal superblock found
> (15354,0):ocfs2_journal_wipe:807 ERROR: status = -22
> (15354,0):ocfs2_check_volume:1610 ERROR: status = -22
> (15354,0):ocfs2_mount_volume:1100 ERROR: status = -22
>
> Any ideas on how to fix this would be appreciated.
>
> Thanks.
>
> _________________________________________________________________
> MSN is giving away a trip to Vegas to see Elton John.  Enter to win 
> today. http://msnconcertcontest.com?icid-nceltontagline
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users