linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Martin Dvořák" <155144@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Cannot get rid of root filesystem LVM snapshot
Date: Sat, 9 Sep 2006 22:49:02 +0200	[thread overview]
Message-ID: <b91808310609091349tf363c5dy57ced3b611523c18@mail.gmail.com> (raw)

Hi all,

I am writing here with hope somebody had already run and successfully
resolved this issue. I am on CentOS 4.4 with kernel
kernel-smp-2.6.9-200.0.2.EL.iworx.x86_64.rpm. I've been in the process
of creating a backup script which uses LVM snapshoting feature to
backup a snapshot of root filesystem instead of live filesystem.

During testing phase on testing CentOS installation, I've been able to
successfully create, mount, unmount and remove root filesystem
snapshots. On live production system, I've also successfully created,
mounted and unmounted root filesystem snapshot, but I CANNOT REMOVE IT
in any way.

lvremove -f gives following output:
[CODE]File descriptor 3 left open
File descriptor 5 left open
File descriptor 7 left open
  /dev/cdrom: open failed: Read-only file system
  Can't remove open logical volume "SSsystem"[/CODE]

tried also to deactivate the snapshot using lvchange -an command:
[CODE]File descriptor 3 left open
File descriptor 5 left open
File descriptor 7 left open
  /dev/cdrom: open failed: Read-only file system
  Can't change snapshot logical volume "SSsystem"[/CODE]

lvdisplay outputs this:
[CODE]File descriptor 3 left open
File descriptor 5 left open
File descriptor 7 left open
  --- Logical volume ---
  LV Name                /dev/VGdb/LVdb
  VG Name                VGdb
  LV UUID                R4mtQ4-Idyo-SRiU-EfLg-TFM6-NZN2-Cd1kgv
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                14.66 GB
  Current LE             469
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:1

  --- Logical volume ---
  LV Name                /dev/VGsystem/LVsystem
  VG Name                VGsystem
  LV UUID                HusBAX-tbxn-6283-zap5-Cihe-K1AX-jKDbk7
  LV Write Access        read/write
  LV snapshot status     source of
                         /dev/VGsystem/SSsystem [active]
  LV Status              available
  # open                 1
  LV Size                31.25 GB
  Current LE             1000
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/VGsystem/SSsystem
  VG Name                VGsystem
  LV UUID                qohvbp-yo1c-SFGv-suM1-9QC9-OwA3-TpX1i0
  LV Write Access        read/write
  LV snapshot status     active destination for /dev/VGsystem/LVsystem
  LV Status              available
  # open                 1
  LV Size                31.25 GB
  Current LE             1000
  COW-table size         2.66 GB
  COW-table LE           85
  Allocated to snapshot  2.32%
  Snapshot chunk size    8.00 KB
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:4[/CODE]

At this very time I am in a situation when the snapshot space is
slowly filling and I am afraid to reboot, manually fill the snapshot
(with hope it will automatically deactivate) or try anything else,
because this is live production system placed in data center and
currently I have no physical access to it - only remote through SSH2.

I'll be grateful for any ideas which might help to resolve this issue
without loosing any data. Thanks very much.

Martin


Here is output of uname -a:
[CODE]Linux xxxx.xxx.xxx 2.6.9-200.0.2.EL.iworxsmp #1 SMP Fri Aug 4
15:25:06 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux[/CODE]

             reply	other threads:[~2006-09-09 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 20:49 Martin Dvořák [this message]
2006-09-09 23:17 ` [linux-lvm] Cannot get rid of root filesystem LVM snapshot Alasdair G Kergon
2006-09-09 23:53   ` Martin Dvořák
2006-09-10 15:41     ` Alasdair G Kergon
2006-09-10 17:35       ` Nix
2006-09-10 21:30         ` Alasdair G Kergon
2006-09-13 19:02           ` Nix

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=b91808310609091349tf363c5dy57ced3b611523c18@mail.gmail.com \
    --to=155144@gmail.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).