I made a RAM disk with mount tmpfs and copied EAH directory there but EAH still accesses the HD every minute thus spinning it up. Is there a way to keep the HD silent while running EAH?
Well, Maybe thare are some other processes that access HDD? (init, cron ?)
If Your machine does nothing, but only EAH, consider running some "liveCD" linux.
1: EAH does some writes to disk (ramdisk), however system has to check all the path from root directory. To do it, it has to read dirs' inodes. This triggers disk read. This shouldn't trigger disk reads if there is a lot of RAM, thus inodes should be cached.
2: if You mount ramdisk on /mnt/ram, and then copy EAH to just /mnt/ram (not deeper eg. /mnt/ram/eah), then writes to file /mnt/ram/FILE triggers update of inode for /mnt/ram (which is on HDD).
I have 1024 MB RAM of which 18 MB is used when I connect. It's a Debian system with 2.6.6 kernel and large memory (4 GB) support is enabled. The HD still spins up when the EAH files are in /home/user/ram/eah. Before they were in /home/user/ram.
> > Write to disk at most every 300 seconds
>
> I tried this with seti and it has no effect with values like 600 or 86400.
Look into sched_request_einstein.phys.uwm.edu.xml in your BOINC folder. This file is only updated when you contact the server, so it might not hold the values. I have no idea if this file holds a checksum, if not you can edit the quoted parameter and restart boinc, otherwise you need to contact the server.
I once tried to check with strace what the program was actually doing, but for whatever reason this caused einstein to stop computing? Strange :-(
However. With strace -e trace=open,close,write,read,access,stat,creat,unlink -p you might be able to see the reason. But as I said, on my machine the einstein client stopped working, so you may have to restart it.
strace ... -ppid reports no activity with boinc and prints SIGALARM and exits with einstein. strace ... boinc prints some initial activity but nothing after that but still every 30 seconds the HD spins up. I set the wait time for spin down to 20 seconds with hdparm.
Running from RAM disk in Linux
)
Well, Maybe thare are some other processes that access HDD? (init, cron ?)
If Your machine does nothing, but only EAH, consider running some "liveCD" linux.
If I don't run EAH the HD
)
If I don't run EAH the HD stays powered off.
Things to think, because i'm
)
Things to think, because i'm not sure of it.
1: EAH does some writes to disk (ramdisk), however system has to check all the path from root directory. To do it, it has to read dirs' inodes. This triggers disk read. This shouldn't trigger disk reads if there is a lot of RAM, thus inodes should be cached.
2: if You mount ramdisk on /mnt/ram, and then copy EAH to just /mnt/ram (not deeper eg. /mnt/ram/eah), then writes to file /mnt/ram/FILE triggers update of inode for /mnt/ram (which is on HDD).
I have 1024 MB RAM of which
)
I have 1024 MB RAM of which 18 MB is used when I connect. It's a Debian system with 2.6.6 kernel and large memory (4 GB) support is enabled. The HD still spins up when the EAH files are in /home/user/ram/eah. Before they were in /home/user/ram.
> If I don't run EAH the HD
)
> If I don't run EAH the HD stays powered off.
Did you try to change this parameter?
Write to disk at most every 300 seconds
You find it here.
> Write to disk at most every
)
> Write to disk at most every 300 seconds
I tried this with seti and it has no effect with values like 600 or 86400.
> > Write to disk at most
)
> > Write to disk at most every 300 seconds
>
> I tried this with seti and it has no effect with values like 600 or 86400.
Look into sched_request_einstein.phys.uwm.edu.xml in your BOINC folder. This file is only updated when you contact the server, so it might not hold the values. I have no idea if this file holds a checksum, if not you can edit the quoted parameter and restart boinc, otherwise you need to contact the server.
I once tried to check with strace what the program was actually doing, but for whatever reason this caused einstein to stop computing? Strange :-(
However. With strace -e trace=open,close,write,read,access,stat,creat,unlink -p you might be able to see the reason. But as I said, on my machine the einstein client stopped working, so you may have to restart it.
strace ... -ppid reports no
)
strace ... -ppid reports no activity with boinc and prints SIGALARM and exits with einstein. strace ... boinc prints some initial activity but nothing after that but still every 30 seconds the HD spins up. I set the wait time for spin down to 20 seconds with hdparm.