"WARNING: Wrong master super block magic" message on boot only

"WARNING: Wrong master super block magic" message on boot only

[Dave Thomas]

I am setting up a new test server with Reiser4 and I have noticed an
error in 'dmesg' when mounting my Reiser4 partition on boot. This is
the error:

"reiser4[mount(1956)]: _init_read_super
(fs/reiser4/init_super.c:198)[nikita-2608]:
WARNING: Wrong master super block magic."

This message only shows up on boot...if I unmount the partition then
mount it again I do not get that error. I ran a 'fsck' on the
partition and everything looked OK...output is at end of message. I
have re-run 'mkfs.reiser4' on the partition but this did not stop the
'warning' message on boot.

I am running Gentoo Linux with gentoo-dev-sources 2.6.8 with
reiser4progs-1.0.1. The Reiser4 partition is a 200GB partition on a
software raid mirror.

Thanks for any help on this,
Dave

Fscking the /dev/md2 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Fri Sep 10 13:15:31 2004
Reiser4 journal (journal40) on /dev/md2: 0 transactions replayed of
the total 0 blocks.
Reiser4 fs was detected on /dev/md2.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           ab01dab7-e10f-400d-8d1a-7a0000000000
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4, ver. 1.0.1
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0x3463fc54
blocks:         50654928
free blocks:    50653339
root block:     23
tail policy:    0x2 (smart)
next oid:       0x10000
file count:     0
tree height:    2
key policy:     LARGE


CHECKING STORAGE TREE
        Read nodes 2
        Nodes left in the tree 2
                Leaves of them 1, Twigs of them 1
        Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
CHECKING EXTENT REGIONS.
        Read twigs 1
        Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
CHECKING SEMANTIC TREE
        Found 1 objects.
        Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
***** fsck.reiser4 finished at Fri Sep 10 13:15:43 2004
Closing fs...done

FS is consistent.

Re: "WARNING: Wrong master super block magic" message on boot only

[Alex Zarochentsev]

Hi,

On Fri, Sep 10, 2004 at 08:26:23PM -0700, Dave Thomas wrote:
> I am setting up a new test server with Reiser4 and I have noticed an
> error in 'dmesg' when mounting my Reiser4 partition on boot. This is
> the error:
> 
> "reiser4[mount(1956)]: _init_read_super
> (fs/reiser4/init_super.c:198)[nikita-2608]:
> WARNING: Wrong master super block magic."
> 
> This message only shows up on boot...if I unmount the partition then
> mount it again I do not get that error. I ran a 'fsck' on the
> partition and everything looked OK...output is at end of message. I
> have re-run 'mkfs.reiser4' on the partition but this did not stop the
> 'warning' message on boot.

do you mean that the system could not mount reiser4 volume at boot time?
or it was only reiser4 warning?

> 
> I am running Gentoo Linux with gentoo-dev-sources 2.6.8 with
> reiser4progs-1.0.1. The Reiser4 partition is a 200GB partition on a
> software raid mirror.
> 
> Thanks for any help on this,
> Dave
> 
> Fscking the /dev/md2 block device.

I can only guess that software raid was not started at the moment of first
attempt to mount it.  Do other fs work well with the same device?

> Will check the consistency of the Reiser4 SuperBlock.
> Will check the consistency of the Reiser4 FileSystem.
> Continue?
> (Yes/No): yes
> ***** fsck.reiser4 started at Fri Sep 10 13:15:31 2004
> Reiser4 journal (journal40) on /dev/md2: 0 transactions replayed of
> the total 0 blocks.
> Reiser4 fs was detected on /dev/md2.
> Master super block (16):
> magic:          ReIsEr4
> blksize:        4096
> format:         0x0 (format40)
> uuid:           ab01dab7-e10f-400d-8d1a-7a0000000000
> label:          <none>
> 
> Format super block (17):
> plugin:         format40
> description:    Disk-format for reiser4, ver. 1.0.1
> magic:          ReIsEr40FoRmAt
> flushes:        0
> mkfs id:        0x3463fc54
> blocks:         50654928
> free blocks:    50653339
> root block:     23
> tail policy:    0x2 (smart)
> next oid:       0x10000
> file count:     0
> tree height:    2
> key policy:     LARGE
> 
> 
> CHECKING STORAGE TREE
>         Read nodes 2
>         Nodes left in the tree 2
>                 Leaves of them 1, Twigs of them 1
>         Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
> CHECKING EXTENT REGIONS.
>         Read twigs 1
>         Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
> CHECKING SEMANTIC TREE
>         Found 1 objects.
>         Time interval: Fri Sep 10 13:15:43 2004 - Fri Sep 10 13:15:43 2004
> ***** fsck.reiser4 finished at Fri Sep 10 13:15:43 2004
> Closing fs...done
> 
> FS is consistent.

-- 
Alex.

Re: "WARNING: Wrong master super block magic" message on boot only

[Dave Thomas]

On Sat, 11 Sep 2004 23:32:17 +0400, Alex Zarochentsev <zam@namesys.com> wrote:
> > This message only shows up on boot...if I unmount the partition then
> > mount it again I do not get that error. I ran a 'fsck' on the
> > partition and everything looked OK...output is at end of message. I
> > have re-run 'mkfs.reiser4' on the partition but this did not stop the
> > 'warning' message on boot.
> 
> do you mean that the system could not mount reiser4 volume at boot time?
> or it was only reiser4 warning?


The partition mounts and functions just fine...I just get the warning.
 

> 
> I can only guess that software raid was not started at the moment of first
> attempt to mount it.  


Interesting point. I'll setup the system so the reiser4 volume is
mounted later in the boot.


> Do other fs work well with the same device?


Yes, the ext3 volumes do not give any errors.

Thanks Alex, I appreciate your response.

Dave

Re: "WARNING: Wrong master super block magic" message on boot only

[Alex Zarochentsev]

On Sun, Sep 12, 2004 at 01:02:37AM -0700, Dave Thomas wrote:
> On Sat, 11 Sep 2004 23:32:17 +0400, Alex Zarochentsev <zam@namesys.com> wrote:
> > > This message only shows up on boot...if I unmount the partition then
> > > mount it again I do not get that error. I ran a 'fsck' on the
> > > partition and everything looked OK...output is at end of message. I
> > > have re-run 'mkfs.reiser4' on the partition but this did not stop the
> > > 'warning' message on boot.
> > 
> > do you mean that the system could not mount reiser4 volume at boot time?
> > or it was only reiser4 warning?
> 
> 
> The partition mounts and functions just fine...I just get the warning.

the warning means that the mount attempt fails.
fs/reiser4/init_super.c:  
...
	} else {
		if (!silent) {
			warning("nikita-2608", "Wrong master super block magic.");
		}

		/* no standard reiser4 super block found */
		brelse(super_bh);
		/* FIXME-VS: call guess method for all available layout
		   plugins */
		/* umka (2002.06.12) Is it possible when format-specific super
		   block exists but there no master super block? */
		return RETERR(-EINVAL);
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...

I think the warning was printed in a failed mount attempt, then reiser4 volume
gets mounted in another (successful) attempt.

Please apply the following patch to see what device was tried:
===== init_super.c 1.35 vs edited =====
--- 1.35/init_super.c	Fri Aug  6 20:51:08 2004
+++ edited/init_super.c	Sun Sep 12 16:55:22 2004
@@ -195,7 +195,7 @@
 		brelse(super_bh);
 	} else {
 		if (!silent) {
-			warning("nikita-2608", "Wrong master super block magic.");
+			warning("nikita-2608", "%s: wrong master super block magic.", s->s_id);
 		}
 
 		/* no standard reiser4 super block found */
======================= 


> > 
> > I can only guess that software raid was not started at the moment of first
> > attempt to mount it.  
> 
> 
> Interesting point. I'll setup the system so the reiser4 volume is
> mounted later in the boot.
> 
> 
> > Do other fs work well with the same device?
> 
> 
> Yes, the ext3 volumes do not give any errors.

the message should be 
"VFS: Can't find ext3 filesystem on dev %s.\n"

> 
> Thanks Alex, I appreciate your response.
> 
> Dave

-- 
Alex.