Date: Sat, 10 Oct 1998 23:48:31 -0600 (MDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: gibbs@pluto.plutotech.com Cc: smp@FreeBSD.ORG Subject: Re: reboot no work Message-ID: <199810110548.XAA12036@panzer.plutotech.com> In-Reply-To: <199810110536.XAA01917@narnia.plutotech.com> from "Justin T. Gibbs" at "Oct 10, 98 11:36:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Justin T. Gibbs wrote... > > Although it sounds similar, this is a different problem. Tom's problem is > > that one of his disks doesn't like the cache sync command. > > I don't see how that can be. We have performed a sync cache on final > device close since CAM came into -current. If you shutdown normally, > the shutdown hook you added should have no effect (all devices should > have seen final close). I don't think that's necessarily the case. (Although it would make sense that all devices would see final close, wouldn't it? :) When I was testing out the shutdown hook changes, I noticed that every time I rebooted, the open flag was cleared for the secondary drive, but not for the boot drive. So, every time I tried it, the cache sync for the boot drive was performed by the shutdown hook, not by daclose(). My guess is that the drive that Tom is having trouble with isn't getting final close, and that's why he hasn't seen this before. I'm not sure what the conditions are that would cause a drive not to see final close when we reboot. It sounds like it might be a bug somewhere. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810110548.XAA12036>