Laptop mode causing writes to wrong sectors?
(Cc: to linux-kernel, in case somebody else is interested in this as well)
Hi Bart,
let me start by stating that the following is mainly guessed. I may be completely wrong. Still I think you may be interested in my observations, and perhaps you already got similar reports?
On my laptop, running 2.6.14, I'm observing some strange file- and filesystem corruptions. First, I thought it may have been caused by an ext3 bug because the first corruption I did observe happened shortly after an ext3 journal replay.
I did report this to linux-kernel, but without any helpful response:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/0129.html
(Subject: ext3 corruption: "JBD: no valid journal superblock found")
But now, I got another hint pointing to a possible cause of this
problem: I found a file - /usr/lib/libatlas.so.3.0 - which was corrupted by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.
As usually the manual pages are only stored compressed, this must have happened when I actually did look at that manual page, which causes the uncompressed version to be written to a file in /tmp/. And the best is:
I actually remember when I did read that man page, and it was while the notebook ran on battery power, which is quite seldom. On battery power, I have laptop mode activated and the hard disk spun down after a short idle time.
Why do I think this is related to the corruption? Well, on the one hand, I'm compiling kernels quite often, tracking linus' git repository, and I'm regularly upgrading my system to debian unstable, both involving hundreds of megabytes of disk writes - and I never observed a single problem while doing so. On the other hand, a simple look at a short manual page did cause file system corruption. This would be rather strange if the corruption happened at random disk writes. But kernel compiles as well as system upgrades involve regular writes to the hard disk, which therefore doesn't spin down. (And additionally, I usually don't do such things while running on battery.) Reading the man page happend while the system was quite idle, and it may have been the read of the compressed image or the write to the temporary file which spun up the hard drive. (To be exact, I looked at the man page more than once - so the second time, the compressed image probably was cached and reading it didn't require filesystem access, so it really could have been the write triggering the spin up)
Well, quite a long mail for a little observation, and sorry if you think that I wasted your time. Did I? Or may my suspicion be true and there is some connection between laptop mode and the corruptions I observe?
Thanks for reading all this stuff ;-)
Jan
Quoted 3 lines · Jan Niehusmann
let me start by stating that the following is mainly guessed. I may be completely wrong. Still I think you may be interested in my observations, and perhaps you already got similar reports?
Nope, no similar reports. But I'm listening. :)
Quoted 8 lines
On my laptop, running 2.6.14, I'm observing some strange file- and filesystem corruptions. First, I thought it may have been caused by an ext3 bug because the first corruption I did observe happened shortly after an ext3 journal replay.
I did report this to linux-kernel, but without any helpful response:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/0129.html
(Subject: ext3 corruption: "JBD: no valid journal superblock found")
Quoting your message:
# There are two things I did with the filesystem which may be related to # this: First, on Oct. 27 I did resize the filesystem (umount, lvextend,
# e2fsck -f, resize2fs, mount). But after that I did several reboots # without any problems - this is my notebook and I turn it on and off # several times a day.
First of all, you having resized your fs is a smoking gun, if you ask me. Your fs is dead/dying, and you know you've recently been tinkering with it. It's the most probable cause.
Secondly, I think that your resize sequence is missing an e2fsck -f after resize2fs. Resizing filesystems is risky business, and I've ruined many a filesystem by resizing them. Even when it came clean out of an fsck. I'm also worried that there was apparently _never_ a full fsck after the resize2fs -- seeing as all the subsequent fscks were probably done by journal. That way, any existing problem can stay in existence and slowly "creep" into more and more of your files as you modify them.
Quoted 3 lines
But now, I got another hint pointing to a possible cause of this
problem: I found a file -/usr/lib/libatlas.so.3.0- which was corrupted
by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.
This sounds like your filesystem's block bitmaps are "fscked up". These problems can definitely cause "creeping corruption" when undetected, because (a) new files overwrite existing files only part of the time (especially if your filesystem has a relatively large amount of free space, as it probably does because you just resized it), and (b) you don't actually use most of your files very often, so you usually don't really notice it until it's too late.
Also, AFAIK the journal is simply a special file as far as ext3 is concerned, and perhaps the journal corruption you experienced has to do with that special file's bits being marked free, and the beginning of the journal being overwritten by other data.
DISCLAIMER: I'm biased. I almost lost a filesystem to this exact problem once. It was ext2resize, not resize2fs. But still.
About the laptop mode hypothesis: I think it's just a coincidence. If it's not, then it could be a "sync-time-only" problem (because what laptop mode does before spindown is a sync), but not a specific laptop mode problem -- laptop mode doesn't influence block numbers whatsoever.
But if it were a sync problem, we would be seeing a lot more reports
of corruption. For now my vote is with the resize. :)
--Bart
Quoted 3 lines · Bart Samwel
First of all, you having resized your fs is a smoking gun, if you ask me. Your fs is dead/dying, and you know you've recently been tinkering with it. It's the most probable cause.
Well, it would be nice if the explanation was that easy - but the recent corruption (with the man page) was on my root partition, which is not on LVM and has never been resized.
Quoted 2 lines
Secondly, I think that your resize sequence is missing an e2fsck -f after resize2fs.
Be assured that at least after the first corruption I observed, I did forced e2fsck on all partitions. Without any errors found.
Quoted 2 lines
after the resize2fs -- seeing as all the subsequent fscks were probably done by journal.
What do you mean with 'by journal'? The filesystems were unmounted (or remounted r/o), so the journal should have been committed and empty at e2fsck time.
Quoted 7 lines
Quoted 4 lines
But now, I got another hint pointing to a possible cause of this
problem: I found a file -/usr/lib/libatlas.so.3.0- which was corrupted by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.This sounds like your filesystem's block bitmaps are "fscked up". These problems can definitely cause "creeping corruption" when undetected,
But this should definitely have been detected by an fsck, right?
Quoted 2 lines
(especially if your filesystem has a relatively large amount of free space, as it probably does because you just resized it)
Root fs is 94% full, and during apt-get upgrade sometimes becomes completely full. (Which I don't like, because it probably causes bad fragmentation...)
Quoted 6 lines
About the laptop mode hypothesis: I think it's just a coincidence. If it's not, then it could be a "sync-time-only" problem (because what laptop mode does before spindown is a sync), but not a specific laptop mode problem -- laptop mode doesn't influence block numbers whatsoever.
But if it were a sync problem, we would be seeing a lot more reports
of corruption. For now my vote is with the resize. :)
I agree it's probably not a sync problem. And therefore, probably not really a laptop-mode bug, even if laptop-mode triggered the corruption. I suspected the hard drive to mess up write requests during spin-up. Or perhaps giving some kind of error message, which could trigger a bug in a rarely tested error-handling path in the kernel. But the fact that you never got similar reports makes this less likely. In the end, I have to consider there may be some bad hardware in my laptop. (Already did a memtest86, of course.)
Jan
Quoted 6 lines · Jan Niehusmann
Quoted 1 line · Bart Samwel
First of all, you having resized your fs is a smoking gun, if you ask me. Your fs is dead/dying, and you know you've recently been tinkering with it. It's the most probable cause.
Well, it would be nice if the explanation was that easy - but the recent corruption (with the man page) was on my root partition, which is not on LVM and has never been resized.
Youch. I assumed this was all the same fs! It is the same HD though?
Quoted 2 lines
Be assured that at least after the first corruption I observed, I did forced e2fsck on all partitions. Without any errors found.
ACK.
Quoted 5 lines
Quoted 1 line
after the resize2fs -- seeing as all the subsequent fscks were probably done by journal.
What do you mean with 'by journal'? The filesystems were unmounted (or remounted r/o), so the journal should have been committed and empty at e2fsck time.
I mean, no full e2fsck, at most a journal replay. This doesn't check the bitmaps, so if they are inconsistent, they stay inconsistent.
Quoted 6 lines
Quoted 4 lines
Quoted 3 lines
But now, I got another hint pointing to a possible cause of this
problem: I found a file -/usr/lib/libatlas.so.3.0- which was corrupted
by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.This sounds like your filesystem's block bitmaps are "fscked up". These problems can definitely cause "creeping corruption" when undetected,
But this should definitely have been detected by an fsck, right?
Yes. And you've had this problem before, even. Googling for "e2fsck block bitmap differences" shows me this as the third entry. :)
http://lkml.org/lkml/2003/8/3/166
If you didn't get those messages, then this is not the problem, apparently.
Quoted 8 lines
I agree it's probably not a sync problem. And therefore, probably not really a laptop-mode bug, even if laptop-mode triggered the corruption. I suspected the hard drive to mess up write requests during spin-up. Or perhaps giving some kind of error message, which could trigger a bug in a rarely tested error-handling path in the kernel. But the fact that you never got similar reports makes this less likely. In the end, I have to consider there may be some bad hardware in my laptop. (Already did a memtest86, of course.)
There is a known problem with laptop mode where, often during spindown/spinup, the kernel emits DMA timeout errors.
http://lkml.org/lkml/2005/8/21/48
According to Andrea Gelmini (the original reporter of this problem) this can lead to system freezes on some kernels, and corruption on others. Are you seeing these errors somewhere in your logs?
What's your hardware? A Thinkpad perhaps?
--Bart
Quoted 1 line · Bart Samwel
Youch. I assumed this was all the same fs! It is the same HD though?
Yes, same HD, same notebook, no hardware changes.
Quoted 8 lines
Quoted 1 line
But this should definitely have been detected by an fsck, right?
Yes. And you've had this problem before, even. Googling for "e2fsck block bitmap differences" shows me this as the third entry. :)
http://lkml.org/lkml/2003/8/3/166
If you didn't get those messages, then this is not the problem, apparently.
Ok - this was on a different computer, so it's not really related, but the important point is that fsck didn't report any errors so the write into the middle of another file was not caused by a bad filesystem.
Quoted 8 lines
There is a known problem with laptop mode where, often during spindown/spinup, the kernel emits DMA timeout errors.
http://lkml.org/lkml/2005/8/21/48
According to Andrea Gelmini (the original reporter of this problem) this can lead to system freezes on some kernels, and corruption on others. Are you seeing these errors somewhere in your logs?
No ide errors at all in the kernel logs, which cover more than one month.
Quoted 1 line
What's your hardware? A Thinkpad perhaps?
ASUS M2400N with a SAMSUNG MP0804H 80GB hard drive (this is not the original hard drive - the notbook was delivered with a 60GB drive). Centrino chipset, 1.6GHz Pentium M. Hard drive running in udma5 mode. 512MB RAM, Intel Pro Wireless 2100 replaced with an Intel Pro Wireless 2200 wireless lan card, and a CardMan 4000 card reader in the pccard slot - not that I think these have any influence on the hard drive, but this is the complete hardware description.
Jan
Quoted 5 lines · Jan Niehusmann
No ide errors at all in the kernel logs, which cover more than one month.
Quoted 1 line
What's your hardware? A Thinkpad perhaps?
Quoted 7 lines
ASUS M2400N with a SAMSUNG MP0804H 80GB hard drive (this is not the original hard drive - the notbook was delivered with a 60GB drive). Centrino chipset, 1.6GHz Pentium M. Hard drive running in udma5 mode. 512MB RAM, Intel Pro Wireless 2100 replaced with an Intel Pro Wireless 2200 wireless lan card, and a CardMan 4000 card reader in the pccard slot - not that I think these have any influence on the hard drive, but this is the complete hardware description.
Thanks. The reason I asked whether it was a Thinkpad is that the DMA problems usually occur on Thinkpads. You don't have a thinkpad, and you don't see the log messages, so that's not it. The filesystem's block bitmaps were OK, so that's not it. Quoting you in your previous message:
# I suspected the hard drive to mess up write requests during spin-up. # Or perhaps giving some kind of error message, which could trigger a
# bug in a rarely tested error-handling path in the kernel. But the fact # that you never got similar reports makes this less likely. In the end, # I have to consider there may be some bad hardware in my laptop.
If there are no other reports on different hardware, then I'm afraid you might be right about the hardware thing. :( I think problems like these usually don't get noticed/fixed because modern Windows versions are actually very lousy at spinning down disks -- in my experience it doesn't really happen, even though you can set the timeouts.
I'm sorry I'm not able to help you out here.
--Bart
Hi!
Quoted 26 lines
let me start by stating that the following is mainly guessed. I may be completely wrong. Still I think you may be interested in my observations, and perhaps you already got similar reports?
On my laptop, running 2.6.14, I'm observing some strange file- and filesystem corruptions. First, I thought it may have been caused by an ext3 bug because the first corruption I did observe happened shortly after an ext3 journal replay.
I did report this to linux-kernel, but without any helpful response:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/0129.html
(Subject: ext3 corruption: "JBD: no valid journal superblock found")But now, I got another hint pointing to a possible cause of this
problem: I found a file -/usr/lib/libatlas.so.3.0- which was corrupted by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.As usually the manual pages are only stored compressed, this must have happened when I actually did look at that manual page, which causes the uncompressed version to be written to a file in
/tmp/. And the best is:
I actually remember when I did read that man page, and it was while the notebook ran on battery power, which is quite seldom. On battery power, I have laptop mode activated and the hard disk spun down after a short idle time.
Quoted 3 lines
Why do I think this is related to the corruption? Well, on the one hand, I'm compiling kernels quite often, tracking linus' git repository, and
Can you try some filesystem test while forcing disk spindowns via hdparm?
It may be bug in laptop mode, or a bug in ide (or something related)... trying spindowns without laptopmode would be helpful.
Pavel
Signature · 1 line
Thanks, Sharp!
Quoted 33 lines · Pavel Machek
Hi!
Quoted 25 lines
let me start by stating that the following is mainly guessed. I may be completely wrong. Still I think you may be interested in my observations, and perhaps you already got similar reports?
On my laptop, running 2.6.14, I'm observing some strange file- and filesystem corruptions. First, I thought it may have been caused by an ext3 bug because the first corruption I did observe happened shortly after an ext3 journal replay.
I did report this to linux-kernel, but without any helpful response:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/0129.html
(Subject: ext3 corruption: "JBD: no valid journal superblock found")But now, I got another hint pointing to a possible cause of this
problem: I found a file -/usr/lib/libatlas.so.3.0- which was corrupted
by 4k of it being overwritten by a different file, which I recognized. And that file happened to be an uncompressed manual page.As usually the manual pages are only stored compressed, this must have happened when I actually did look at that manual page, which causes the uncompressed version to be written to a file in
/tmp/. And the best is:
I actually remember when I did read that man page, and it was while the notebook ran on battery power, which is quite seldom. On battery power, I have laptop mode activated and the hard disk spun down after a short idle time.Quoted 3 lines
Why do I think this is related to the corruption? Well, on the one hand, I'm compiling kernels quite often, tracking linus' git repository, and
Quoted 6 lines
Can you try some filesystem test while forcing disk spindowns via hdparm?
It may be bug in laptop mode, or a bug in ide (or something related)... trying spindowns without laptopmode would be helpful.
I don't know if it would be helpful, but I run several servers with multiple drives, usually 4-5, some of which are in RAID and some aren't, and they all spin down and restart without problems many times a day. The kernel is 2.6.14.? with one patch to get my unsupported VIA IDE working.
My laptop also has a spindown (five min from memory) and I have yet to have a problem with it. Don't know if any of that is "spindowns without laptopmode" in a useful sense.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Hi!
Quoted 6 lines
Quoted 6 lines
Can you try some filesystem test while forcing disk spindowns via hdparm?
It may be bug in laptop mode, or a bug in ide (or something related)... trying spindowns without laptopmode would be helpful.
Quoted 8 lines
I don't know if it would be helpful, but I run several servers with multiple drives, usually 4-5, some of which are in RAID and some aren't, and they all spin down and restart without problems many times a day. The kernel is 2.6.14.? with one patch to get my unsupported VIA IDE working.
My laptop also has a spindown (five min from memory) and I have yet to have a problem with it. Don't know if any of that is "spindowns without laptopmode" in a useful sense.
Unless you can also reproduce the failure... no, probably does not help much.
Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
Quoted 4 lines · Pavel Machek
Quoted 1 line
My laptop also has a spindown (five min from memory) and I have yet to have a problem with it. Don't know if any of that is "spindowns without laptopmode" in a useful sense.
Unless you can also reproduce the failure... no, probably does not help much.
Okay, let's recap.
* There are a lot of people who are not having problems. The people who *are* having problems can usually reproduce them. My interpretation: the problem is triggered by some hardware and/or kernel config settings.
* A significant proportion of the people who *do* have trouble see messages about DMA timeouts. The problems do also occur on other hardware, but seem to be most pronounced on Thinkpad T40s. On those machines, the DMA timeout problems are triggered *especially* when the madwifi drivers are loaded (see http://bugzilla.ubuntu.com/show_bug.cgi?id=6108).
Perhaps I should start collection kernel configs and hardware specs, see if there are any unexpected commonalities. The influence of the madwifi drivers suggest that we could be be looking for anything really. What do you think?
--Bart
Quoted 21 lines · Bart Samwel
Quoted 6 lines · Pavel Machek
Quoted 3 lines
My laptop also has a spindown (five min from memory) and I have yet to have a problem with it. Don't know if any of that is "spindowns without laptopmode" in a useful sense.
Unless you can also reproduce the failure... no, probably does not help much.
Okay, let's recap.
* There are a lot of people who are not having problems. The people who *are* having problems can usually reproduce them. My interpretation: the problem is triggered by some hardware and/or kernel config settings.
* A significant proportion of the people who *do* have trouble see messages about DMA timeouts. The problems do also occur on other hardware, but seem to be most pronounced on Thinkpad T40s. On those machines, the DMA timeout problems are triggered *especially* when the madwifi drivers are loaded (see
http://bugzilla.ubuntu.com/show_bug.cgi?id=6108).
Quoted 4 lines
Perhaps I should start collection kernel configs and hardware specs, see if there are any unexpected commonalities. The influence of the madwifi drivers suggest that we could be be looking for anything really. What do you think?
The issue might be that these people are using
hdparm -S xxx
or
hdparm -y / -Y
while a much better way to do
hdparm -B 63
The -S option should in theory be safe, but I remember some drives did behave unpredictably if this was used. -y/-Y is much tougher and some drives will not work reliably unless first woken up manually before issuing a read/write request.
On the other hand, -B is pretty safe on drives that support it, and all IBM notebook drives do.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 6 lines · Vojtech Pavlik
The issue might be that these people are using
hdparm -S xxx
or
Quoted 8 lines
hdparm -y / -Y
while a much better way to do
hdparm -B 63
The -S option should in theory be safe, but I remember some drives did behave unpredictably if this was used.
Well, some drives have a specific lower limit on the -S values that are supported. That's the only compatibility problem I've ever encountered with -S. (And you can find out if a drive has a lower limit by checking hdparm -i.)
Quoted 3 lines
-y/-Y is much tougher and some
drives will not work reliably unless first woken up manually before issuing a read/write request.
In fact, -Y is problematic but -y usually isn't. -Y puts the drive to sleep and requires that Linux reset the complete IDE controller before using it again, while -y simply puts the drive in standby mode, leaving it up to the drive to decide when it spins up. I've never heard of any problems with -y.
Quoted 2 lines
On the other hand, -B is pretty safe on drives that support it, and all IBM notebook drives do.
Not true, unfortunately. In fact, I had to change the default config of laptop-mode-tools a while ago so that it wouldn't use -B, as it seemed to be one of the *causes* of hangup/corruption problems. This was also an issue on Thinkpads, and I think it was also noted in the ubuntu bug I linked to earlier.
An additional problem is that the values for -B are not really standardized, while the values for -S are.
--Bart
Quoted 6 lines · Bart Samwel
* A significant proportion of the people who *do* have trouble see messages about DMA timeouts. The problems do also occur on other hardware, but seem to be most pronounced on Thinkpad T40s. On those machines, the DMA timeout problems are triggered *especially* when the madwifi drivers are loaded (see
http://bugzilla.ubuntu.com/show_bug.cgi?id=6108).
That's interesting. Both Bradley and me are using ipw2200, an in the madwifi thread, one person also mentions he is using this driver. I don't know if madwifi and ipw2200 use common or very similar code. But perhaps this problem really is caused by a combination of laptop mode / disk spinup and certain wireless drivers?
As far as I remember all corruptions I observed happened while being connected to wireless lan. But that alone never triggered the bug, I had to enable laptop mode as well.
Unfortunately, I still have to find a way to reliably trigger the problem. None of my test scripts which try to trigger disk activity while the drive is spun down caused any corruption yet.
Jan
Quoted 5 lines · Jan Niehusmann
That's interesting. Both Bradley and me are using ipw2200, an in the madwifi thread, one person also mentions he is using this driver. I don't know if madwifi and ipw2200 use common or very similar code. But perhaps this problem really is caused by a combination of laptop mode / disk spinup and certain wireless drivers?
Perhaps this one is related?
http://bughost.org/bugzilla/show_bug.cgi?id=821
If the corruption caused by this bug could lead to the filesystem corruption I observed, it would match my observations quite well:
- Corruption started shortly after I upgraded to a kernel with ipw2200 driver version 1.0.8
- Happens when using wireless
- File system corruption happens with laptop mode (because then the probability that dirty pages which will be written to disk later can be overwritten before the write actually happens is much higher)
- Problem is difficult to reproduce, as it's not deterministic which type of data structure gets overwritten, and it can happen only once per reboot (or driver reload)
Question is, could this bug cause filesystem corruption without any Oops visible in the kernel log? Cc: to Zhu Yi at Intel - can you answer this question?
Jan
Quoted 3 lines · Jan Niehusmann
Question is, could this bug cause filesystem corruption without any Oops visible in the kernel log? Cc: to Zhu Yi at Intel - can you answer this question?
OK, can this bug overwrite a page containing filesystem metadata? The way it looks to me, it can: it writes at some fixed distance after a block of memory allocated by the driver, and that memory could probably be anything.
Now, can the stuff go to disk without oopsing? In the case of ext3, the metadata writeback is handled by the JBD layer, which is block-based and doesn't care about the actual page contents AFAIK -- that's handled by the ext3 filesystem layer. That means a corrupted metadata page can go to disk without oopsing. Youch. :/
Remaining issue: this bug is only triggered when the ipw2200 driver does firmware restarts, which generates kernel output "ipw2200: Firmware error detected. Restarting". Jan, Bradley, do you see any of these messages in your logs near the time of corruption? That should be within 10 minutes before it; the corruption may happen anywhere during a spun-down period. (Or does the ipw2200 driver only show this message in debug mode?)
--Bart
Quoted 4 lines · Bart Samwel
Remaining issue: this bug is only triggered when the ipw2200 driver does firmware restarts, which generates kernel output "ipw2200: Firmware error detected. Restarting". Jan, Bradley, do you see any of these messages in your logs near the time of corruption? That should be within
The "Firmware error detected" message occurs regularly - fortunately, on my system they cause no significant performance problem. If I understand the code correctly, writes to the wrong memory location only happen at the first firmware restart. (Unless certain debugging flags are set, which isn't the case here.) So, basically, it happens exactly once after each reboot, after a few minutes of network activity.
It's difficult to know the exact time when the filesystem corruption happened, as it usually isn't noticed immediately.
Jan
Quoted 12 lines · Pavel Machek
Hi!
Quoted 8 lines
Quoted 8 lines
Can you try some filesystem test while forcing disk spindowns via hdparm?
It may be bug in laptop mode, or a bug in ide (or something related)... trying spindowns without laptopmode would be helpful.
Quoted 10 lines
Quoted 5 lines
I don't know if it would be helpful, but I run several servers with multiple drives, usually 4-5, some of which are in RAID and some aren't, and they all spin down and restart without problems many times a day. The kernel is 2.6.14.? with one patch to get my unsupported VIA IDE working.
My laptop also has a spindown (five min from memory) and I have yet to have a problem with it. Don't know if any of that is "spindowns without laptopmode" in a useful sense.
Unless you can also reproduce the failure... no, probably does not help much.
No, that was really the point, even on multiple systems using spindown, I have no failures. I see four possible causes:
1 - spindown
2 - laptop mode
3 - 1 + 2
4 - bad hardware, kernel not at fault
Since I have a lot of (1) data I thought eliminating that as a cause by itself might be helpful.
Signature · 3 lines
bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979