From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] drive-spindown
Date: Wed Sep 25 08:22:50 2002 [thread overview]
Message-ID: <20020925151529.A30084@sistina.com> (raw)
In-Reply-To: <200209251151.25358.michael@frotscher.net>; from michael@frotscher.net on Wed, Sep 25, 2002 at 11:51:25AM +0200
On Wed, Sep 25, 2002 at 11:51:25AM +0200, Michael Frotscher wrote:
> On Wednesday 25 September 2002 11:25, Heinz J . Mauelshagen wrote:
>
> > that could be either some regular access to extents residing on hdb
>
> So you are saying that the volume can be used (like accessing hdb) even
> though hdc is spun down?
Correct.
If there's just accesses to extents mapped onto hdb (i.e. from the filesystem),
hdc will never spin up (unless somthing outside LVM triggers it ;-)
> But if, it is a good explanation as my volume still has plenty of space
> so hdc would not be accessed until hdb is full.
See "pvdisplay -v /dev/hd[bc]" or "lvdisplay -v YourLV" for your
logical volume(s) to see what is mapped onto what.
> --
> Cheers,
>
> Michael
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-09-25 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 3:18 [linux-lvm] drive-spindown Michael Frotscher
2002-09-25 4:35 ` Heinz J . Mauelshagen
2002-09-25 5:05 ` Michael Frotscher
2002-09-25 8:22 ` Heinz J . Mauelshagen [this message]
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=20020925151529.A30084@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.com \
/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