[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4692221B.7050608@dgreaves.com>
Date: Mon, 09 Jul 2007 12:55:07 +0100
From: David Greaves <david@...eaves.com>
To: Bruce Allen <ballen@...vity.phys.uwm.edu>
Cc: Mark Lord <liml@....ca>, Douglas Gilbert <dougg@...que.net>,
Tejun Heo <htejun@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Jeff Garzik <jeff@...zik.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jan Dvorak <fermentol@...il.com>,
Smartmontools Mailing List
<smartmontools-support@...ts.sourceforge.net>,
Klaus Fuerstberger <kfuerstberger@...or.de>,
Bruce Allen <bruce.allen@....mpg.de>
Subject: Re: SMART problems in 2.6.22
Hi Bruce
>> From some of the earlier threads that I missed (below) I have the
> impression that the problem may be a very simple one, namely that
> starting with 2.6.22 one needs to run a command to enable SMART when a
> box is first booted -- the kernel no longer does this as part of the
> init/setup of the disks. But that is NOT consistent with the first two
> reports above, which show 'SMART ENABLED'.
>
> Here are some of the earlier threads that I completely missed:
>
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg164863.html
This is mine and although it's a 'real' problem, it is something that's easy to
hack around by having the suspend script turn on smart after it is resumed. (Of
course I can't use resume until a skge wol bug is fixed so I won't see/test this
unless asked too.)
The smart init scripts run '-s on' when the system boots anyway for my system -
this problem only occurs for me during suspend/resume. Maybe smartd should
detect that as Alan says.
Please let me know if there's anything else you need.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists