From: "Peter" <sw98234-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org
Subject: Re: reiser4: mount -o remount,ro / causes error on reboot
Date: Wed, 13 Sep 2006 09:31:40 +0000 (UTC) [thread overview]
Message-ID: <ee8j5s$ibt$1@sea.gmane.org> (raw)
In-Reply-To: 45077170.1070301@slaphack.com
On Tue, 12 Sep 2006 21:48:16 -0500, David Masover wrote:
snip...
>> Sorry to report this as an r4 bug, although it's interesting to note that
>> the 1.12.4 baselayout did NOT cause this problem in reiserfs3.6
>
> Mine was doubtlessly a Reiser4 bug, as it resulted in either an oops or
> a panic, I'm not sure which. I think it was an oops, and after that
> oops, the disk is inaccessible. Since it's a root FS, this is a
> problem! The init scripts should not be able to cause this, no matter
> how buggy they are.
>
That's good to know...I guess :)
>
> I haven't done this already, because everything works now, and no one's
> asked me to yet.
I find this curious, don't you?
I'm wondering if kernel preemption settings and anticipatory read ahead
settings could play a role? Mine are CONFIG_PREEMPT=y and
CONFIG_DEFAULT_IOSCHED=CFQ. One other thing of note is that my kernel has
Jens Axboe's iosched-rollup-2.6.17.4-2 patch. My reiser4 patch is
2.6.17-3. The iosched patch removed a lot of dma messages in the kernel
log (not disk errors).
Anyway, whatever changed in my downgraded baselayout, at least it's not
causing reiser4 to hiccup. Curious problem in that it only occurs
immediately after a shutdown, not after the error and a reboot from a
maintenance prompt.
--
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via
jabber: pete4abw at jabber.org
ICQ: 73676357
next prev parent reply other threads:[~2006-09-13 9:31 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
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 [this message]
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='ee8j5s$ibt$1@sea.gmane.org' \
--to=sw98234-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
--cc=reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org \
/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.