All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Uhlig <juhlig@parc.com>
To: linux-lvm@redhat.com
Cc: sunsa@parc.com
Subject: [linux-lvm] problem creating lvm2 snapshot volume
Date: Tue, 29 Jun 2004 08:07:51 PDT	[thread overview]
Message-ID: <40E185C7.8060606@parc.com> (raw)

Hi.

We are trying to install lvm2 volumes on our fedora core 2 (kernel 
2.6.6-1.435smp)
Dell 2650 poweredge fileservers. Following the instructions at:
    http://tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html
...do not work and the following error occurs:

[juhlig@aragami ~]$ lvcreate -L592M -s -n dbbackup /dev/VG_aragami_1/LV_1
  device-mapper ioctl cmd 9 failed: Invalid argument
  Couldn't load device 'VG_aragami_1-dbbackup'.
  Problem reactivating origin LV_1

This error causes the LV Status to go to "suspended" and the snapshot 
volume cannot
be removed without rebooting the system. If anyone can help us resolve 
this problem
it would be greatly appreciated as we are under pressure to bring these 
servers on-line
ASAP.

thanks, John Uhlig

------------------------------------------
test config volume details below:
-----------------------------------------

BEFORE snapshot lvcreate.
------------------------------------
[juhlig@aragami ~]$ vgdisplay
  --- Volume group ---
  VG Name               VG_aragami_1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  39
  VG Access             read/write
  VG Status             resizable
  MAX LV                255
  Cur LV                1
  Open LV               0
  Max PV                255
  Cur PV                1
  Act PV                1
  VG Size               273.43 GB
  PE Size               4.00 MB
  Total PE              69999
  Alloc PE / Size       25600 / 100.00 GB
  Free  PE / Size       44399 / 173.43 GB
  VG UUID               J7Z9Fw-oool-q9tk-Dzqy-LOwu-Hv8N-MWv6vH
                                                                                                       

[juhlig@aragami ~]$ lvdisplay
  --- Logical volume ---
  LV Name                /dev/VG_aragami_1/LV_1
  VG Name                VG_aragami_1
  LV UUID                t4Xi36-MIe2-zYIM-BN6F-gpwC-1Umr-xeMEtE
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                100.00 GB
  Current LE             25600
  Segments               1
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           253:1
---------------------------------------
AFTER snapshot create error:
---------------------------------------
[juhlig@aragami ~]$ lvdisplay
  --- Logical volume ---
  LV Name                /dev/VG_aragami_1/LV_1
  VG Name                VG_aragami_1
  LV UUID                t4Xi36-MIe2-zYIM-BN6F-gpwC-1Umr-xeMEtE
  LV Write Access        read/write
  LV snapshot status     source of
                         /dev/VG_aragami_1/dbbackup [INACTIVE]
  LV Status              suspended
  # open                 0
  LV Size                100.00 GB
  Current LE             25600
  Segments               1
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           253:1
   
  --- Logical volume ---
  LV Name                /dev/VG_aragami_1/dbbackup
  VG Name                VG_aragami_1
  LV UUID                vDdYvc-Kfo0-au04-n4k2-c2UY-ikSC-3CEzwv
  LV Write Access        read/write
  LV snapshot status     INACTIVE destination for /dev/VG_aragami_1/LV_1
  LV Status              available
  # open                 0
  LV Size                100.00 GB
  Current LE             25600
  Segments               1
  Snapshot chunk size    8.00 KB
  Allocated to snapshot  100.00%
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           253:3

             reply	other threads:[~2004-06-29 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 15:07 John Uhlig [this message]
2004-06-29 15:21 ` [linux-lvm] problem creating lvm2 snapshot volume Dimitar Katerinski

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=40E185C7.8060606@parc.com \
    --to=juhlig@parc.com \
    --cc=linux-lvm@redhat.com \
    --cc=sunsa@parc.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.