Prev: What's that clicking noise?
Next: testing
From: E Z Peaces on 30 Nov 2009 19:20
Daniel Cohen wrote:

> For my own use, if I have the Seagate drive running at all, I never want
> it to sleep. And for that purpose there are two possilbe solutions (both
> of which I found on MacUpdate). There's a free one called IIRC
> KeepDriveSpinning that does what it says but is mildly tricky to turn
> off, and a paid one that is easier to turn on and off.
>

Thank you! I wondered why I hadn't seen such a utility before. If it
were just a 5-second spin-up time, I wouldn't mind, but the delays can
be 36 seconds.
From: nospam on 30 Nov 2009 21:57
In article <hf1n2v$q6u$1(a)news.eternal-september.org>, E Z Peaces
<cash(a)invalid.invalid> wrote:

> >> I wish I could keep the disk awake. Spinning takes very little power,
> >> and spinning up probably means wear and tear as well as a delay.
> >
> > it's actually less wear unless it's spinning down and up every few
> > minutes.
>
> How did you find out? Manufacturers state reliability in hours of
> typical use and numbers of spin-up cycles, but not in hours of spinning.
> Don't bearings run on a film of air? Each spin-up means a
> temperature change.

a non-spinning disk has *no* wear.

there's a balance between repeated spin-down/spin-up every few minutes
and having it spin down when not in use and spin up some number of
hours later. the latter will extend the life of drive, especially if
it's spun down for a while, like overnight.
From: thepixelfreak on 1 Dec 2009 13:59
On 2009-12-01 10:41:35 -0800, thepixelfreak <not(a)dot.com> said:

> On 2009-12-01 03:49:56 -0800, dempson(a)actrix.gen.nz (David Empson) said:
>> The 'fs_usage' command via Terminal is likely to be the best plan of
>> attack. You need to have it running, then do something on the Dock which
>> triggers a wakeup of the external drive, then look at what fs_usage
>> reports about the same time.

So with:

fs_usage -f filesys | grep Volumes

I see the following when I invoke Dictionary.app *either* from the Dock
or directly from the shell via 'open /Applications/Dictionary.app'.

10:45:04 open /Volumes/black
hole/.fseventsd/000000000fecfcbd
0.000007 fseventsd
10:45:04 open /Volumes/black
hole/.fseventsd/000000000ff05a3e
0.000008 fseventsd
10:45:04 open /Volumes/black
hole/.fseventsd/000000000ff05a3e
0.000007 fseventsd
10:45:04 open /Volumes/black
hole/.fseventsd/000000000ff31bda
0.000010 fseventsd
10:45:04 open
/Volumes/archive/.fseventsd/000000000f88d246
0.000013 fseventsd
10:45:04 open
/Volumes/archive/.fseventsd/000000000fa3930d
0.000009 fseventsd
10:45:04 open
/Volumes/archive/.fseventsd/000000000fa3ceb1
0.000008 fseventsd
10:45:04 open
/Volumes/archive/.fseventsd/000000000fa3f7c8
0.000009 fseventsd
10:45:04 open
/Volumes/scratch/.fseventsd/000000000f8c2dd8
0.000013 fseventsd
10:45:04 open
/Volumes/scratch/.fseventsd/000000000fa1209c
0.000009 fseventsd
10:45:04 open
/Volumes/scratch/.fseventsd/000000000fa3cebd
0.000008 fseventsd
10:45:04 open
/Volumes/scratch/.fseventsd/000000000fa3f7c2
0.000008 fseventsd

It does this for *every* external drive. There is no man page on
fseventsd. It seems that it is started by launchd on boot. Someone on
the web stated they configure it to ignore external drives. I haven't
found any clues as to how that is done yet.

I *do* have spotlight and time machine configured to ignore my eternal drives.
--

thepixelfreak

From: thepixelfreak on 1 Dec 2009 14:26
On 2009-12-01 10:59:41 -0800, thepixelfreak <not(a)dot.com> said:

> On 2009-12-01 10:41:35 -0800, thepixelfreak <not(a)dot.com> said:
>
>> On 2009-12-01 03:49:56 -0800, dempson(a)actrix.gen.nz (David Empson) said:
>>> The 'fs_usage' command via Terminal is likely to be the best plan of
>>> attack. You need to have it running, then do something on the Dock which
>>> triggers a wakeup of the external drive, then look at what fs_usage
>>> reports about the same time.
> <snip>
> 10:45:04 open
> /Volumes/scratch/.fseventsd/000000000fa1209c
> 0.000009 fseventsd
> 10:45:04 open
> /Volumes/scratch/.fseventsd/000000000fa3cebd
> 0.000008 fseventsd
> 10:45:04 open
> /Volumes/scratch/.fseventsd/000000000fa3f7c2
> 0.000008 fseventsd
>
> It does this for *every* external drive. There is no man page on
> fseventsd. It seems that it is started by launchd on boot. Someone on
> the web stated they configure it to ignore external drives. I haven't
> found any clues as to how that is done yet.
>
> I *do* have spotlight and time machine configured to ignore my eternal drives.

http://arstechnica.com/apple/reviews/2007/10/mac-os-x-10-5.ars/7

"To prevent events from being logged at all for changes to a particular
volume, simply create a file named no_log in the .fseventsd directory
on that volume. And in case it doesn't go without saying, FSEvents
honors the Mac OS X access control rules; you cannot receive events
about directories that you don't have permission to read."
--

thepixelfreak

From: Daniel Cohen on 1 Dec 2009 14:55
E Z Peaces <cash(a)invalid.invalid> wrote:

> I wonder if a utility could be written to keep an external disk awake by
> having the Mac ask it something every few minutes.

See my post elsewhere in the thread.
--
<http://www.decohen.com>
Send e-mail to the Reply-To address.
Mail to the From address is never read.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: What's that clicking noise?
Next: testing