[Ocfs2-users] Problem after upgrade to 1.4.7-1 (Bad magic number in superblock while opening context for device)

Sunil Mushran sunil.mushran at oracle.com
Tue Apr 20 09:23:16 PDT 2010


Your setup may not have persistent device naming. You can
use blkid or mounted.ocfs2 to discover the ocfs2 devices.

Marcus Alves Grando wrote:
> Hello Guys,
>
> After upgrade to 1.4.7-1 my FS does not mount anymore. Just after 
> upgrade rpm, FS mount and works fine, but after reboot server, it does 
> not work anymore.
>
> FS are created with ocfs2-1.4.4 and ocfs2-tools-1.4.3-1. If I downgrade 
> to old version doesn't work too.
>
> Messages when trying to mount with new version:
>
> # mount /d01
> mount.ocfs2: Device name specified was not found while opening device 
> LABEL=020017B000
> # fsck.ocfs2 -n /dev/mapper/mpath3p1
> fsck.ocfs2 1.4.4
> fsck.ocfs2: Bad magic number in superblock while opening 
> "/dev/mapper/mpath3p1"
>
> If you need more info, please let me know. I think it's easy to reproduce.
>
> Best regards
>
>   




More information about the Ocfs2-users mailing list