Bug 308153

Summary:	sys-apps/smartmontools-5.39 multiple bugs; version bump to 5.39.1
Product:	Gentoo Linux	Reporter:	Boney McCracker <brendlerjg>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://sourceforge.net/apps/trac/smartmontools/browser/tags/RELEASE_5_39_1/smartmontools/NEWS
Whiteboard:
Package list:		Runtime testing required:	---

Description Boney McCracker 2010-03-07 05:20:59 UTC

The smartctl --quietmode option broke with the upgrade from 5.38 to 5.39.

As a result, people who cron 'smartctl' rather than unnecessarily running the nasty brobdingagian 'smartd' daemon, to get gratuitous cron output.

Version 5.39.1, which fixes this bug (and others, such as broken '-l selftest') became available 28 January.


Reproducible: Always

Steps to Reproduce:
With version 5.39...

smartd -q errorsonly -H /dev/sda

Actual Results:  
tempest ~ # smartctl -q errorsonly -H /dev/sda
smartctl 5.39 2009-12-09 r2995 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

tempest ~ #

Expected Results:  
With version 5.38...

twister ~ # smartctl -q errorsonly -H /dev/sda
twister ~ #

Refer to:

http://sourceforge.net/apps/trac/smartmontools/browser/tags/RELEASE_5_39_/smartmontools/NEWS

"8	Date 2010-01-28
9	Summary: smartmontools release 5.39.1
10	-----------------------------------------------------------
11	- Fix crash on kFreeBSD.
12	- Fix regression in smartctl option '-q, --quietmode'.
13	- Fix regression in smartd directive '-l selftest'.
14	- Linux: Allow smartd 'DEVICESCAN -d sat'.
15	- Linux: Fix spin-up of SATA drive if '-n standby' is used."

Comment 1 Samuli Suominen (RETIRED) gentoo-dev

2010-03-07 05:38:46 UTC


*** This bug has been marked as a duplicate of bug 305405 ***

Comment 2 Boney McCracker 2010-03-07 06:49:24 UTC

(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of bug 305405 ***
> 

Sorry about the duplicate.  I did search, but apparently didn't do it right.