From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Peter <sw98234@hotmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4: mount -o remount,ro / causes error on reboot
Date: Mon, 11 Sep 2006 11:30:39 +0400 [thread overview]
Message-ID: <200609111130.39647.vs@namesys.com> (raw)
In-Reply-To: <ee1vth$dgb$2@sea.gmane.org>
Hello
On Monday 11 September 2006 01:26, Peter wrote:
> On Sun, 10 Sep 2006 15:12:00 -0500, David Masover wrote:
> > Peter wrote:
> >> Using: gentoo
> >> kernel 2.6.17.11 with beyond patchset
> >> reiser patch 2.6.17-3
> >> reiser4progs 1.0.5
> >>
> >> At the end of the gentoo shutdown script is a short function which
> >> remounts / as ro.
> >
> > There's also one in the Gentoo startup script, which attempts to remount
> > / ro, then remount it rw. I commented that out, because it was causing
> > similar problems. I figure if it runs sync when it shuts down, that's
> > good enough.
>
> The errors I note only occur on shutdown (halt.sh) not startup.
Sorry, I am confused. In the first mail you said:
"On reboot or after a poweroff, root does not mount properly, and after
some modules are loaded, there are segfaults when running init scripts."
This looks like you have problems on startup. Would you, please, describe the
sequence of operations which leads to the problem with more details.
> Do you
> think it could be an IDE timing thing similar to what was described on
> another thread on this ml? What's interesting is that this problem is
> recent and I am trying to look back and see what system-level packages
> were updated recently (I just converted to the 2006.1 profile before this
> occured and that caused a lot of programs to recompile. A week earlier,
> it was gcc-4.1.1. I know base layout was updated recently). Maybe something
> in mount changed? The shutdown scripts look the same. Something is left
> unhinged somewhere. Glad I was not hallucinating! Thanks for confirming
> for me.
>
> > Still, it's an annoying problem, I think it's a kernel oops. Namesys,
> > what kind of information would be helpful?
>
> Yes, it's annoying and disconcerting at the same time. If it was a kernel
> oop then, wouldn't it have shown itself earlier? I
next prev parent reply other threads:[~2006-09-11 7:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 17:01 reiser4: mount -o remount,ro / causes error on reboot Peter
2006-09-10 20:12 ` David Masover
2006-09-10 21:26 ` Peter
2006-09-11 7:30 ` Vladimir V. Saveliev [this message]
2006-09-11 10:09 ` Peter
2006-09-11 11:10 ` Sander Sweers
2006-09-11 11:43 ` Peter
2006-09-11 12:21 ` Peter
2006-09-11 15:12 ` Peter
2006-09-12 21:10 ` Peter
2006-09-12 21:32 ` Peter
2006-09-13 2:48 ` David Masover
2006-09-13 9:31 ` Peter
2006-09-13 10:49 ` Vladimir V. Saveliev
2006-09-13 11:32 ` Peter
2006-09-13 13:18 ` Peter
2006-09-14 11:37 ` Peter
2006-09-17 18:45 ` Jussi Suutari-Jääskö
2006-09-18 9:52 ` Peter
2006-09-18 15:14 ` Peter
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=200609111130.39647.vs@namesys.com \
--to=vs@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sw98234@hotmail.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.