I'm not sure if this is applicable, but the symptoms are somewhat similar to something I ran into in the past...
If you by chance had a new kernel installed, which did not take effect until the next reboot, then it may a version incompatibility between the kernel and the driver. Show us the output of: uname -a Also indicate the specific OCFS2 packages (include all the numbers) that you have installed. At 02:00 PM 4/20/2010, you wrote: >Date: Tue, 20 Apr 2010 12:36:21 -0300 >From: Marcus Alves Grando <marcus.gra...@terra.com.br> >Subject: [Ocfs2-users] Problem after upgrade to 1.4.7-1 (Bad magic >number in superblock while opening context for device) > >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 > >-- >Marcus Alves Grando >Suporte Engenharia Latam - Terra Networks Brasil S/A >+55 51 3284-4238 > >Qual ? a sua Terra? _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
