From: Alex Zarochentsev <zam@namesys.com>
To: Dave Thomas <linuxsense@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: "WARNING: Wrong master super block magic" message on boot only
Date: Sun, 12 Sep 2004 17:07:56 +0400 [thread overview]
Message-ID: <20040912130755.GT6294@backtop.namesys.com> (raw)
In-Reply-To: <676b8ab0409120102326e5b16@mail.gmail.com>
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.
prev parent reply other threads:[~2004-09-12 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 3:26 "WARNING: Wrong master super block magic" message on boot only Dave Thomas
2004-09-11 19:32 ` Alex Zarochentsev
2004-09-12 8:02 ` Dave Thomas
2004-09-12 13:07 ` Alex Zarochentsev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040912130755.GT6294@backtop.namesys.com \
--to=zam@namesys.com \
--cc=linuxsense@gmail.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.