linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM disk power management
Date: Mon, 09 Feb 2015 09:54:07 +0100	[thread overview]
Message-ID: <54D875AF.8010705@redhat.com> (raw)
In-Reply-To: <646AF90A-464B-44EC-BE14-FCD4F888A3CB@gmail.com>

Dne 8.2.2015 v 19:59 Drew... napsal(a):
> Hi,
> I have 3 physical disks forming one volume group, with one logical volume.
> If i try to issue a standby command to the logical volume i get the following
> error..
>
> |sudo hdparm -y /dev/mapper/VG0-LVstorage
>
> /dev/mapper/VG0-LVstorage:
>
>   issuing standby command
>
>   HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device|
>
>
> But if i issue a standby command to the individual disks in the volume group..
>
> |sudo hdparm -y /dev/sda1 /dev/sdb1 /dev/sdc1
>
> /dev/sda1:
>
>   issuing standby command
>
> /dev/sdb1:
>
>   issuing standby command
>
> /dev/sdc1:
>
>   issuing standby command|
>
> This works fine!
> Is addressing individual disks the normal way to to spin down disks in a lvm
> volume group or will this cause file corruption.
> And if not, is there a safe way to achieve this or is it just not possible to
> spin down disks in a lvm.
> I would be grateful of any advice you could offer. I have spent some time
> searching around for some information on this & i can not find any documented
> on this anywhere.
> Thanks,


Yes - you need to 'hdparm' control  'real' devices/PVs.
There is no point to try to control logical volumes.
Imagine you could have 1000LVs on a single PV.


Regards

Zdenek

      reply	other threads:[~2015-02-09  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 18:59 [linux-lvm] LVM disk power management Drew...
2015-02-09  8:54 ` Zdenek Kabelac [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=54D875AF.8010705@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).