udev/udevadm trigger led to disks being unable to spin down for more than a second
(Semi-crosspost from the Gentoo forums, I rewrote this text, though.)
Here's everything I did:
http://forums.gentoo.org/viewtopic-p...4.html#6117744 (TL;DR: added two udev rules matching my MAC addresses and renaming eth* to net/lan, and ran "udevadm trigger net".)
Nothing whatsoever was related to the disk subsystem, except for, most likely, "udevadm trigger net" which appears to scan through a vast amount of device nodes, including all disks and partitions, according to "udevadm trigger --dry-run --verbose net".
The system has an uptime of 214 days, and the problem started within 5 minutes (that's how often I log the disk status) of me running udevadm, so hardly a coincidence.
They are three SATA disks, by the way.
The three disks are in a md RAID5 array, but the array is stopped and as such not mounted, and iostat shows *no* disk activity when they are spun up.
As soon as I try to spin them down (hdparm -y /dev/sdX), they start spinning again within 0.5-4 seconds at most... with the exception that I somehow, for a totally unknown reason, managed to get sdc to be in standby for a few hours now. I have no clue why it's that particular disk out of the three; they are different models, but equally sized, same partitions (100% to the RAID array), etc.
(Actually, I tried that again; sdb and sdd spun up, sdc is still in standby.
sdb is a WD Green 1TB (WD10EADS)
sdc is a Hitachi 7K1000(.B?) 1TB
sdd is a Hitachi 7K1000(.B?) 1TB
Anyone have a solution in mind - except for rebooting and hoping for the best?
|All times are GMT -5. The time now is 04:33 PM.|