From: Goswin von Brederlow <goswin-v-b@web.de>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Sat, 22 Aug 2009 08:37:16 +0200 [thread overview]
Message-ID: <87zl9sjqw3.fsf@frosties.localdomain> (raw)
In-Reply-To: <20090822050416.GA9202@musti.tarvainen.info> (Tapani Tarvainen's message of "Sat, 22 Aug 2009 08:04:17 +0300")
Tapani Tarvainen <raid@tapanitarvainen.fi> writes:
> Just a data point: I've got a box (Debian Lenny) with five disks,
> system disk plus 4-disk RAID5 array, used as a backup server
> (rsnapshot), and I power the disks in the raid array down after
> running the backup - and they stay powered down, even though I don't
> umount the filesystems let alone stop the array. When accessed (like
> for restoring something from the backup), they wake up, so I've got an
> hourly cron job powering them down again - but most days (when
> there're no restores) they are powered up only during the backup run.
>
> So it can be done. It's not filesystem type dependent either, there's
> one jfs and one ext3 in the array.
>
> The system disk stays up, though. Some experimenting suggested
> that getting it to stay down would require putting /tmp and parts
> of /var on a ramdisk (/var/log at least), but I didn't go to
> the trouble of tracking down all disk-awakening services.
Same here. I have a raid1 for the system on 2 drives and a raid5 over
6 drives for data. The raid5 is ext3 powers down after 15 minutes
without access. The raid1 stays up all the time due to /var/log/syslog
being written to too often. /tmp is tmpfs though.
MfG
Goswin
next prev parent reply other threads:[~2009-08-22 6:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 16:35 linux disk access when idle Matt Garman
2009-08-20 18:45 ` Richard Scobie
2009-08-21 16:59 ` Matt Garman
2009-08-21 17:01 ` Ric Wheeler
2009-08-22 21:04 ` Matt Garman
2009-08-23 18:23 ` Bill Davidsen
2009-08-26 19:45 ` Matt Garman
2009-08-22 6:33 ` Goswin von Brederlow
2009-08-21 6:42 ` Henry, Andrew
2009-08-21 8:17 ` Jon Hardcastle
2009-08-21 16:35 ` Foster_Brian
2009-08-21 17:31 ` Matt Garman
2009-08-21 17:22 ` Matt Garman
2009-08-21 22:00 ` Bill Davidsen
2009-08-21 23:10 ` Matt Garman
2009-08-21 23:13 ` Carl A. Cook
2009-08-22 1:41 ` berk walker
2009-08-22 2:07 ` John Robinson
2009-08-22 4:28 ` Richard Scobie
2009-08-22 5:04 ` Tapani Tarvainen
2009-08-22 6:37 ` Goswin von Brederlow [this message]
2009-08-24 18:07 ` Billy Crook
2009-08-22 5:02 ` Kyle Liddell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zl9sjqw3.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox