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
