Re: RE: Completely spinning down an EIDE hard drive

["adwint pandora be" <adwint pandora be>]

------------------------
 redhat-install-list redhat com wrote:
------------------------
	
>> >
>> >I guess other automatic things could cause some issues, like any cron
>> >job, etc.
>>
>> More fundamental than that is if you read a file you update the
>> ATIME (access time) value in its inode. That will cause a disk access
>> when the cached inode is flushed.
>>
>> The same is true for directories. If you perform a directory listing
>> or any operation that implies this, such as using wildcards or
>> command line auto-completion, that will update the ATIME value
>> resulting eventually in a disk write.
>>
>> There is a noatime option you can specify for mount and in /etc/fstab
>> to turn this ATIME updating off for a filesystem.
>>
>> >Can I tell the history program to write somewhere other than my home
>> >directory?
>>
>> That would be bash or whatever shell you are using.
>>
>> Lawrence
>
>Lawrence,
>   Certainly, and disk access, be it a read or a write, would presumably
>have to cause the disk to eventually spin up if it was in a low power, spin
>down state.
>
>   What I noticed last evening was that after switching to -S 12 (for a auto
>spin-down delay of 60 seconds) that the drive would spin down much later
>than 1 minute - more like 5 minutes, but would then immediately spin up
>again a few seconds later. This would repeat every 5-10 minutes.
>
>   I don't believe that I had an user level processes running that nominally
>cause disk access. I normally run SetiAtHome, but for the sake of testing
>this had stopped that one. Everything else that was running was just
>standard issue Linux.

Seti Home? I used to run it on my XP machines; I did about 147 WU (work units). Sadly, I haven't been able to install it on my Linux box; it's not an RPM and it comes without any installation manual.  In XP it takes just a couple of clicks.

I really would like to have Seti running again, can you please tell me how to get it installed.  It may be simple, but I have no idea.

Albert
>
>   Certainly this test isn't the exact scenario I originally raised. I'm
>fine with having a 1394 drive spinning, but my system isn't configured that
>way yet. My current thought is that maybe only the /boot partition needs to
>be on the EIDE drive with everything else on 1394. After booting I normally
>dismount /boot anyway, so nothing should trigger that drive to do anything I
>think.
>
>   Interesting task for the weekend. (After I discuss it with a few of the
>1394 developers. It turns out none of them have used 1394 under Linux for
>anything like this. Only data storage...)
>
>Cheers,
>Mark
>
>
>
>_______________________________________________
>Redhat-install-list mailing list
>Redhat-install-list redhat com
>https://www.redhat.com/mailman/listinfo/redhat-install-list
>To Unsubscribe Go To ABOVE URL or send a message to:
>redhat-install-list-request redhat com
>Subject: unsubscribe
>