ok thuh Freak, did exactly as you said. then I decided to reboot so I could make sure this w process is not running. It did not fix the problem as my hdd never spin down. Then I decided to do a fs_usage:
I get this just about every second:
03:33:23 select 1.000047 W cupsd
here's a snippet. As you can see, sometimes, the W update is followed by the cron scheduler. I don't know if they are in fact related though, cause most of the time W update shows up without cron.
Code:
03:34:00 stat tabs 0.000060 cron
03:34:00 stat private/etc/crontab 0.000036 cron
03:34:00 CACHE_HIT 0.000082 WindowServer
03:34:00 CACHE_HIT 0.000021 WindowServer
03:34:00 CACHE_HIT 0.000022 WindowServer
03:34:00 CACHE_HIT 0.000010 WindowServer
03:34:00 CACHE_HIT 0.000013 WindowServer
03:34:00 CACHE_HIT 0.000009 WindowServer
03:34:00 CACHE_HIT 0.000023 WindowServer
03:34:00 CACHE_HIT 0.000010 WindowServer
03:34:00 CACHE_HIT 0.000008 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:01 select 1.000036 W cupsd
03:34:00 CACHE_HIT 0.000082 WindowServer
03:34:00 CACHE_HIT 0.000023 WindowServer
03:34:00 CACHE_HIT 0.000022 WindowServer
03:34:00 CACHE_HIT 0.000010 WindowServer
03:34:00 CACHE_HIT 0.000013 WindowServer
03:34:00 CACHE_HIT 0.000010 WindowServer
03:34:00 CACHE_HIT 0.000020 WindowServer
03:34:00 CACHE_HIT 0.000008 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000007 WindowServer
03:34:00 CACHE_HIT 0.000120 WindowServer
03:34:00 CACHE_HIT 0.000023 WindowServer
03:34:00 WrData 0.003416 W update
03:34:01 CACHE_HIT 0.000060 WindowServer
03:34:01 CACHE_HIT 0.000019 WindowServer
03:34:01 CACHE_HIT 0.000020 WindowServer
03:34:01 CACHE_HIT 0.000009 WindowServer
03:34:01 CACHE_HIT 0.000013 WindowServer
03:34:01 CACHE_HIT 0.000010 WindowServer
03:34:01 CACHE_HIT 0.000024 WindowServer
03:34:01 CACHE_HIT 0.000010 WindowServer
03:34:01 CACHE_HIT 0.000007 WindowServer
03:34:01 CACHE_HIT 0.000007 WindowServer
03:34:01 CACHE_HIT 0.000007 WindowServer
03:34:01 CACHE_HIT 0.000007 WindowServer
03:34:01 WrData 0.000256 W update
03:34:01 sync 0.258678 W update
03:34:01 WrMeta[async] 0.001092 W update
03:34:01 WrMeta[async] 0.001136 W update
03:34:01 WrMeta[async] 0.001335 W update
03:34:01 WrMeta[async] 0.001508 W update
03:34:01 WrMeta[async] 0.001664 W update
03:34:01 WrMeta[async] 0.001882 W update
I noted though, some things were different (dunno if it's due to the change of name of w):
Code:
03:31:31.226 WrMeta[async] D=0x00002778 B=0x1000 /dev/disk0s9 0.001193 W update
03:31:31.226 WrMeta[async] D=0x0000b468 B=0x2000 /dev/disk0s9 0.001366 W update
03:31:31.227 WrMeta[async] D=0x00011878 B=0x2000 /dev/disk0s9 0.001491 W update
03:31:31.227 WrMeta[async] D=0x00016658 B=0x2000 /dev/disk0s9 0.001603 W update
03:31:31.227 WrMeta[async] D=0x0001a0c8 B=0x2000 /dev/disk0s9 0.001754 W update
notice how it says /dev/disk0s9. I believe this means it's doing somethnig to my startup volume.
Hmm... I'm not sure what to do right now. Seems like things are relatively unchanged. Thanks a lot for your help thuh Freak, I really appreciate it. do you think it might be a hardware problem? Cause because this was a fresh install, other people should have it too. I wouldn't assume my comp would be any different. Please reply, thanks again.