At Fri, 12 Aug 2011 22:35:12 +0100 (BST) CentOS mailing list
wrote:
>
> On Fri, 12 Aug 2011, Robert Heller wrote:
>
> *snip*
>
> >>> The disk's *firmware* updated itself. So long as the *disk* is powered
> >>> up and spinning, its *firmware* is 'running' (or runs when the disk is
> >>> acces
On Fri, 12 Aug 2011, Robert Heller wrote:
*snip*
>>> The disk's *firmware* updated itself. So long as the *disk* is powered
>>> up and spinning, its *firmware* is 'running' (or runs when the disk is
>>> accessed or something like that). Modern disks are a long, long way
>>> from the simple MFM
At Fri, 12 Aug 2011 20:36:25 +0100 (BST) CentOS mailing list
wrote:
>
> On Fri, 12 Aug 2011, Robert Heller wrote:
>
> > The disk's *firmware* updated itself. So long as the *disk* is powered
> > up and spinning, its *firmware* is 'running' (or runs when the disk is
> > accessed or something l
On Fri, 12 Aug 2011, Robert Heller wrote:
> The disk's *firmware* updated itself. So long as the *disk* is powered
> up and spinning, its *firmware* is 'running' (or runs when the disk is
> accessed or something like that). Modern disks are a long, long way
> from the simple MFM drives of the 19
On Fri, 12 Aug 2011 08:11:58 -0400
Robert Heller wrote:
> The disk's *firmware* updated itself.
...
> Appearently, palimpsest does some of what smartctl does: accesses the
> SMART data on the drive. This is completely independent of smartd.
> Smartd is a daemon that runs in the background and
At Thu, 11 Aug 2011 22:24:23 -0600 CentOS mailing list
wrote:
>
> On Fri, 12 Aug 2011 04:05:47 +
> Joseph L. Casale wrote:
>
> > I think you misunderstood the first reply: smartd, as in the init script is
> > a
> > means to alert root of pending issues, _it_ doesn't present the data, _tha
>Which still doesn't answer my question. Perhaps I'm wording it poorly -- I'll
>try again:
Perhaps palimpsest runs smartctl and queries the device itself? Perhaps it
borrowed
code from the project and runs the query itself? I don't have any servers with
GUI's,
couldn't tell you...
_
On Fri, 12 Aug 2011 04:05:47 +
Joseph L. Casale wrote:
> I think you misunderstood the first reply: smartd, as in the init script is a
> means to alert root of pending issues, _it_ doesn't present the data, _that_
> init script simply checks it and reports it. You don't need it running to
> ma
>As smartd isn't running in the default Centos configuration, where does
>palimpsest get its information? Is it a self-contained program that doesn't
>require smartd or is something else happening behind the scenes?
I think you misunderstood the first reply: smartd, as in the init script is a
me
On Thu, 11 Aug 2011 20:42:46 -0400
Robert Heller wrote:
> Almost all modern disk are S.M.A.R.T capable. What this means is that
> various information about the disk, mostly relating to its health can be
> monitored. This includes things like sector errors. If smartd is
> running root will get E
At Thu, 11 Aug 2011 17:57:59 -0600 CentOS mailing list
wrote:
>
> I notice that the smartd service is not running by default on a new
> installation. But palimpsest seems to get updated statistics every so often as
> when I check the statistics on a drive it says "last updated" some number of
>
11 matches
Mail list logo
