From: Bruce A. <ba...@gr...> - 2004-03-04 19:34:01
|
Hans-Peter, Please check the current CVS version. You should be able to use smartctl -F $t -d 3ware,0 -a /dev/sda > smart.sda.$t with that, and get different results for all three choices. Bruce On Thu, 4 Mar 2004, Hans-Peter Jansen wrote: > On Thursday 04 March 2004 13:39, Bruce Allen wrote: > > > On Thursday 04 March 2004 02:56, Bruce Allen wrote: > > > > > -F samsung doesn't make a difference to -F samsung2, both > > > > > differ in one parameter to -F none: > > > > > > > > They should make a difference in the self-test log. Please > > > > check. > > > > > > Hmm, here's, what I did: > > > # for t in none samsung samsung2; do > > > > > > > smartctl -F $t -d 3ware,0 -a /dev/sda > smart.sda.$t > > > > done > > > > > > # diff smart.sda.samsung smart.sda.samsung2 > > > # echo $? > > > 0 > > > > Hans-Peter, sadly this is a bug. Turns out it has been there for a > > long time, too. > > No problem, I'm a happy bug hitter, as long as it doesn't destroy > my data ;-) > > > I've just coded up a fix, but I want to absolutely confirm the > > problem. Could you please try the same thing but with: > > > > smartctl -P ignore -v 9,halfminutes -F $t -d 3ware,0 -a /dev/sda > > > smart.sda.$t > > Done, now they differ: > --- smart.sda.samsung 2004-03-04 15:13:59.000000000 +0100 > +++ smart.sda.samsung2 2004-03-04 15:14:00.000000000 +0100 > @@ -68,8 +68,6 @@ > 201 Soft_Read_Error_Rate 0x000b 100 100 051 Pre-fail Always - 0 > > SMART Error Log Version: 1 > -Warning: ATA error count 1 inconsistent with error log pointer 5 > - > ATA Error Count: 1 > CR = Command Register [HEX] > FR = Features Register [HEX] > @@ -95,13 +93,19 @@ > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name > -- -- -- -- -- -- -- -- --------- -------------------- > - b1 c0 00 01 00 00 a0 00 337379.328 DEVICE CONFIGURATION RESTORE > - 80 00 01 01 00 00 a0 00 337379.328 [VENDOR SPECIFIC] > - ec 00 03 01 00 00 a0 00 337379.328 IDENTIFY DEVICE > - 91 00 3f 01 00 00 af 00 337379.328 INITIALIZE DEVICE PARAMETERS [OBS-6] > - 10 00 00 01 00 00 a0 00 337379.328 RECALIBRATE [OBS-4] > + b1 c0 00 01 00 00 a0 00 7.188 DEVICE CONFIGURATION RESTORE > + 80 00 01 01 00 00 a0 00 7.188 [VENDOR SPECIFIC] > + ec 00 03 01 00 00 a0 00 7.188 IDENTIFY DEVICE > + 91 00 3f 01 00 00 af 00 7.188 INITIALIZE DEVICE PARAMETERS [OBS-6] > + 10 00 00 01 00 00 a0 00 7.188 RECALIBRATE [OBS-4] > > SMART Self-test log structure revision number 1 > -No self-tests have been logged. [To run self-tests, use: smartctl -t] > - > +Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > +# 1 Short offline Completed without error 00% 446 - > +# 2 Short offline Completed without error 00% 244 - > +# 3 Short offline Completed without error 00% 221 - > +# 4 Extended offline Completed without error 00% 202 - > +# 5 Short offline Completed without error 00% 199 - > +# 6 Short offline Completed without error 00% 177 - > +# 7 Short offline Completed without error 00% 154 - > > > --- smart.sda.none 2004-03-04 15:13:59.000000000 +0100 > +++ smart.sda.samsung2 2004-03-04 15:14:00.000000000 +0100 > @@ -68,9 +68,7 @@ > 201 Soft_Read_Error_Rate 0x000b 100 100 051 Pre-fail Always - 0 > > SMART Error Log Version: 1 > -Warning: ATA error count 256 inconsistent with error log pointer 5 > - > -ATA Error Count: 256 (device log contains only the most recent five errors) > +ATA Error Count: 1 > CR = Command Register [HEX] > FR = Features Register [HEX] > SC = Sector Count Register [HEX] > @@ -84,7 +82,7 @@ > Timestamp = decimal seconds since the previous disk power-on. > Note: timestamp "wraps" after 2^32 msec = 49.710 days. > > -Error 256 occurred at disk power-on lifetime: 0 hours > +Error 1 occurred at disk power-on lifetime: 0 hours > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > > > Funny is, with -F samsung, the smart error log is missing, while > -F none seem to only get the error count wrong.. > > > The problem is that if a '-F' option is preset (as it is for your > > drive), then giving a different '-F' option on the command line > > does not over-ride it UNLESS -P ignore is specified. Fortunately > > this is easy to fix. > > > > Hans-Peter, if you can confirm the problem I'm going to send you a > > tarball to try with your original test, OK? > > I've no problem with CVS, just tell me the branch, if it's not HEAD, > when you're ready, or just send me a unified diff ;-) > > > (Note to Phil only: I've already coded a fix. If Hans confirms the > > problem like to you check my fix after it's in CVS). > > > > Cheers, > > Bruce > > Till then, > Pete > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |