Re: [Smartmontools-support]Segmentation fault

[Bruce Allen <ballen@gr...>]

Hi Tom,

> Hi, just thought I'd give a little information about a problem I
> encountered running smartd on my system.
> 
> Here are the specifics:
> RedHat 9 with 2.4.20 kernel
> Only hard drive is a Seagate ST340017A (not in smartctl/smartd database)
> Nforce IDE chipset
> smartmontools 5.1-18
> 
> When running smartd with the following smartd.conf, I get a segmentation
> fault:
> 
> DEVICESCAN -H -l error -m tmaddox@... -P ignore

Well, you have the dubious honor of having found the first "real" bug in
5.1-18.  Looks like it's time for 5.19 (we are changing the release
numbering system).

I've just fixed this bug in the code base.  A good workaround is to add
"-o on" to the line above. This will enable auto-offline testing on any
drives that support it, probably a "good thing".

My apologies -- this was a programming oversight on my part.

Bruce

[Smartmontools-support]Segmentation fault

[Tom Maddox <tmaddox@th...>]

Hi, just thought I'd give a little information about a problem I
encountered running smartd on my system.

Here are the specifics:
RedHat 9 with 2.4.20 kernel
Only hard drive is a Seagate ST340017A (not in smartctl/smartd database)
Nforce IDE chipset
smartmontools 5.1-18

When running smartd with the following smartd.conf, I get a segmentation
fault:

DEVICESCAN -H -l error -m tmaddox@... -P ignore

The same configuration worked fine on a RedHat 7.3 system with a 2.4.18
kernel with SCSI drives but not in a system with IDE.  The culprit
appears to be the "-l error," since the segfaults stopped when I removed
that directive.

Any thoughts?

Thanks,

Tom

Re: [Smartmontools-support]Segmentation fault

[Bruce Allen <ballen@gr...>]

Hi Tom,

> Hi, just thought I'd give a little information about a problem I
> encountered running smartd on my system.
> 
> Here are the specifics:
> RedHat 9 with 2.4.20 kernel
> Only hard drive is a Seagate ST340017A (not in smartctl/smartd database)
> Nforce IDE chipset
> smartmontools 5.1-18
> 
> When running smartd with the following smartd.conf, I get a segmentation
> fault:
> 
> DEVICESCAN -H -l error -m tmaddox@... -P ignore

Well, you have the dubious honor of having found the first "real" bug in
5.1-18.  Looks like it's time for 5.19 (we are changing the release
numbering system).

I've just fixed this bug in the code base.  A good workaround is to add
"-o on" to the line above. This will enable auto-offline testing on any
drives that support it, probably a "good thing".

My apologies -- this was a programming oversight on my part.

Bruce