Your message dated Fri, 28 Apr 2006 12:42:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in unstable
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: smartmontools
Version: 5.32-1
Severity: normal

The significant line in my smartd.conf is:

DEVICESCAN \
        -a \
        -o on \
        -S on \
        -n standby \
        -s (see below) \
        -m zblaxell \
        -M test \
        -M diminishing \

I've tried various values for the parameter of '-s', including:

        -s 
'./../.././..|S/../.././(01|07|13|19)|C/../.././(02|10|18)|O/../.././03'
        -s 
'L/../.././00|S/../.././(01|07|13|19)|C/../.././(02|10|18)|O/../.././03'
        -s 'L/../.././..'
        -s '.*'

None of these cause smartd to actually perform long self-tests, nor
do they cause smartd to write a message to the log explaining why no
self-test was performed.  All other self-test types trigger some activity
by smartd, which either commands the drive to perform the test, or writes
in the syslog an excuse for not attempting the test (e.g. drive already
doing a test, drive in STANDBY mode, drive not capable of self-test).

If the -s regexp matches a long self-test for a given hour, it will
prevent all other test types that also match in the same hour.  The 
parameters "-s '.*'" seem to mean "run no self-tests."

I've stared at the code for a while but I can't see an obvious reason why
smartd would schedule a short self-test but not a long one, nor any reason
why there wouldn't be at least one line of syslog mentioning that smartd
had at least considered running the long self-test, but decided not to.

I'm running smartmontools 5.32 on several machines with kernel versions
2.4.20, 2.4.22, 2.4.24, 2.4.26, and 2.6.7.

-- Package-specific info:
Ouput of /usr/share/bug/smartmontools:
# CONFIG_IDE_TASK_IOCTL is not set

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (102, 'testing'), (101, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-zb-586-smp
Locale: LANG=C, LC_CTYPE=C

Versions of packages smartmontools depends on:
ii  libc6                       2.3.2.ds1-13 GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi,
this bug should be fixed in the latest upload to unstable.
Cheers,
 -- Guido

--- End Message ---

Reply via email to