Bug 122966
Summary: | logout+restart cycles power to IDE disks unnecessarily | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | barryn, devscott, exodus, gczarcinski, k.georgiou, mitr, oliva, p.van.egdom, reivec, robe, sindrepb, thomasz, thorn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-06-09 09:59:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Reiser
2004-05-10 19:28:58 UTC
Not only wear and tear. In my case, the BIOS often fails to bring the disks back up, such that I can't reliably reboot the boxes. I've experienced such problems on boxes with A7V133 MoBos, one of them with one HD on the VIA IDE controller and one HD on the Promise controller (both ATA100); the other box with far many more disks, including a few Sil0680 ATA133 controllers. The reboot is slow, bcause the disks are turned on one after the other, and it takes several seconds for each, and quite often the BIOS times out or something like that waiting for a disk to come back up and won't complete the boot, so manual interaction is required (Ctrl-Alt-Del). The 2.4 code only forced this flush on shutdowns, not on reboots. Can't we tell the difference and proceed accordingly? Sure not flushing on reboot leaves a window of opportunity for disk corruption due to power failure after the kernel reboots and before the disks complete the flush, but this opportunity already exists in case of power failure before or while the kernel forces the flush, so it's not such a big deal IMHO. *** Bug 123608 has been marked as a duplicate of this bug. *** This is a bug in the initscripts package and affects all platforms. It's actually the kernel reboot/shutdown code that does this, totally by itself. initscripts have nothing to do with it. Rats, clicked on commit to soon. I also meant to point out that the problem appears to be that the kernel had no way to distinguish between the shutdown and the reboot cases. I saw some patches in lkml floating around that were meant to fix this, but I think they were post-2.6.6. Maybe we could merge them into an update kernel that might be issued for FC2 at some point in the future? I filed a kernel bug report at http://bugme.osdl.org/show_bug.cgi?id=2732 I'd like to comment that this bug only manifests itself with ATA drives, on my system the hard drives on my SCSI interface do not have a problem. *** This bug has been marked as a duplicate of 123873 *** *** Bug 123873 has been marked as a duplicate of this bug. *** Was that actually neccessary to change what was a dup of what Alexandre. All the important information is now in Bug 123873 which isnt the first one people will find. Grumble 8) This was the one with a link to the osdl.org bug submission, that has a link back to this one, so I thought it would be better this way. We don't want the link to the upstream bug report buried in one of a dozen dups that this one might get. Seems like there's a patch available: From http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.6-bk8.log: ChangeSet, 2004-05-20 22:22:11-07:00, akpm [PATCH] ide-disk.c: don't put disks in STANDBY mode on reboot From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz.edu.pl> From: Rene Herman <rene.herman> Prevent the disks from spinning down across a reboot. verified, works for me. I guess we can close this bug. has a new kernel been issued to the development rpms yet? Yes, fc-devel has new kernels (.422 last time I checked) *** Bug 125487 has been marked as a duplicate of this bug. *** Does the new kernel in updates, kernel-2.6.6-1.427, fix this issue? If it does shouldn't this bug be marked as resolved, and not Rawhide? > Does the new kernel in updates, kernel-2.6.6-1.427, fix this issue? Yes. > If it does shouldn't this bug be marked as resolved, and not Rawhide? This bug *is* closed. (AFAIK the Red Hat Bugzilla setup does not make a distinction between CLOSED and RESOLVED.) And RAWHIDE is the correct resolution -- this bug was resolved by an update in rawhide, and the fact that the update has now been released doesn't change that. (Perhaps my explanation is not correct, but the answer still is -- CLOSED/RAWHIDE is the correct state for this bug to be in.) |