All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] rootfs on lvm2 and vgchange: Can't deactivate volume group "vg_sys" with 4 open logical volume(s)
Date: Thu, 24 Jun 2004 15:48:25 +0200	[thread overview]
Message-ID: <200406241548.26342.arekm@pld-linux.org> (raw)

Hi,

I'm using kernel 2.6.7 with lvm2:
[root@anduril /root]# lvm version
  LVM version:     2.00.17 (2004-06-20)
  Library version: 1.00.17-ioctl (2004-04-19)
  Driver version:  4.1.0

[root@anduril /root]# lvdisplay -C
  LV      VG     Attr   LSize  Origin Snap%  Move Copy%
  lv_home vg_sys -wi-ao 25.00G
  lv_root vg_sys -wi-ao  3.00G
  lv_tmp  vg_sys -wi-ao  2.00G
  lv_var  vg_sys -wi-ao 15.00G

root filesystem is on LVM (on lv_root) so I'm starting lvm from initrd:
LVM_SYSTEM_DIR=/tmp lvm vgscan --ignorelockingfailure
LVM_SYSTEM_DIR=/tmp lvm vgchange --ignorelockingfailure -a y vg_sys
it works fine.

Then when my initrscripts run vgscan && vgchange -a y to activate potential 
other vgs it complains:
Can't deactivate volume group "vg_sys" with 4 open logical volume(s)

I have no idea why it want's deactivate it if the command is ,,-a y'' so the 
task it to activate it. Reasonable would be: if active then do not touch.

[root@anduril /root]# vgchange -ay vg_sys
  Can't deactivate volume group "vg_sys" with 4 open logical volume(s)
[root@anduril /root]# lvchange -a y vg_sys/lv_tmp
[root@anduril /root]# lvchange -a y vg_sys/lv_home
[root@anduril /root]# lvchange -a y vg_sys/lv_var
[root@anduril /root]# lvchange -a y vg_sys/lv_root

vgchange -ay with verbose below.

(tested cvs version of lvm2 from today, too - same results)

      Setting log/indent to 1
      Setting log/prefix to
      Setting log/command_names to 0
      Setting global/test to 0
      Setting log/overwrite to 0
      log/activation not found in config: defaulting to 0
    Logging initialised at Thu Jun 24 15:33:55 2004

      Setting global/umask to 63
    Set umask to 0077
      Setting devices/dir to /dev
      Setting global/proc to /proc
      Setting global/activation to 1
      global/suffix not found in config: defaulting to 1
      global/units not found in config: defaulting to h
        Matcher built with 3 dfa states
      Setting devices/cache to /etc/lvm/.cache
      Setting devices/write_cache_state to 1
        Opened /etc/lvm/.cache
        Closed /etc/lvm/.cache
        /dev/md5: Added to device cache
        /dev/md10: Added to device cache
        /dev/md6: Added to device cache
        /dev/md11: Added to device cache
        /dev/md13: Added to device cache
        /dev/md14: Added to device cache
        /dev/md12: Added to device cache
        /dev/md3: Added to device cache
        /dev/md4: Added to device cache
        /dev/md7: Added to device cache
        /dev/md2: Added to device cache
        /dev/md8: Added to device cache
        /dev/md9: Added to device cache
        /dev/md0: Added to device cache
        /dev/md15: Added to device cache
        /dev/md1: Added to device cache
        /dev/sda3: Added to device cache
     Loaded persistent filter cache from /etc/lvm/.cache
      Setting activation/reserved_stack to 256
      Setting activation/reserved_memory to 8192
      Setting activation/process_priority to -18
      global/format not found in config: defaulting to lvm2
      Setting backup/retain_days to 30
      Setting backup/retain_min to 10
      Setting backup/archive_dir to /etc/lvm/archive
      Setting backup/backup_dir to /etc/lvm/backup
      global/fallback_to_lvm1 not found in config: defaulting to 0
        Processing: vgchange -ay
      Setting global/locking_type to 1
      Setting global/locking_dir to /var/lock/lvm
      File-based locking enabled.
    Finding all volume groups
        Opened /dev/md0
      /dev/md0: lvm2 label detected
        Closed /dev/md0
        Opened /dev/md0
        Closed /dev/md0
        Opened /dev/md1
      /dev/md1: No label detected
        Closed /dev/md1
        Opened /dev/md2
        /dev/md2: Failed to read label area
        Closed /dev/md2
        Opened /dev/sda3
      /dev/sda3: No label detected
        Closed /dev/sda3
        Opened /dev/md3
        /dev/md3: Failed to read label area
        Closed /dev/md3
        Opened /dev/md4
        /dev/md4: Failed to read label area
        Closed /dev/md4
        Opened /dev/md5
        Closed /dev/md5
        Opened /dev/md6
        /dev/md6: Failed to read label area
        Closed /dev/md6
        Opened /dev/md7
        /dev/md7: Failed to read label area
        Closed /dev/md7
        Opened /dev/md8
        /dev/md8: Failed to read label area
        Closed /dev/md8
        Opened /dev/md9
        /dev/md9: Failed to read label area
        Closed /dev/md9
        Opened /dev/md10
        /dev/md10: Failed to read label area
        Closed /dev/md10
        Opened /dev/md11
        /dev/md11: Failed to read label area
        Closed /dev/md11
        Opened /dev/md12
        /dev/md12: Failed to read label area
        Closed /dev/md12
        Opened /dev/md13
        /dev/md13: Failed to read label area
        Closed /dev/md13
        Opened /dev/md14
        /dev/md14: Failed to read label area
        Closed /dev/md14
        Opened /dev/md15
        /dev/md15: Failed to read label area
        Closed /dev/md15
        Opened /dev/sdb3
      /dev/sdb3: No label detected
        Closed /dev/sdb3
      Locking /var/lock/lvm/V_vg_sys RB
    Finding volume group "vg_sys"
       Opened /dev/md0
      /dev/md0: lvm2 label detected
        Read vg_sys metadata (8) from /dev/md0 at 12800 size 1526
      Setting activation/missing_stripe_ filler to /dev/ioerror
        Getting device info for vg_sys-lv_root
        dm version
        dm info  
7b2WBEINyPBBRuKukOXhSWueVI3JB5e4FwgXeHy0sAYxJflPHN9DvBjabZxkYffR
        Getting device info for vg_sys-lv_tmp
        dm info  
7b2WBEINyPBBRuKukOXhSWueVI3JB5e4bqO2jZql5IkzuwrXfs0D6HC6Z7NbYW72
        Getting device info for vg_sys-lv_var
        dm info  
7b2WBEINyPBBRuKukOXhSWueVI3JB5e4DKzs8YXx6YeA32MhS1p7wQlTkv7VvJMV
        Getting device info for vg_sys-lv_home
        dm info  
7b2WBEINyPBBRuKukOXhSWueVI3JB5e4UqLQ7XDesIb6t7u5wJNVx9c9VScs83Lx
      Unlocking /var/lock/lvm/V_vg_sys
        Closed /dev/md0
      Dumping persistent device cache to /etc/lvm/.cache


-- 
Arkadiusz Mi�kiewicz     CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

             reply	other threads:[~2004-06-24 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 13:48 Arkadiusz Miskiewicz [this message]
2004-06-24 15:01 ` [linux-lvm] rootfs on lvm2 and vgchange: Can't deactivate volume group "vg_sys" with 4 open logical volume(s) Alasdair G Kergon

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=200406241548.26342.arekm@pld-linux.org \
    --to=arekm@pld-linux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.