All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben <benscott@nwlink.com>
To: lvm-devel@redhat.com
Subject: Excessive lvreduce on snapshot doesn't show up as invalid snapshot
Date: Sun, 04 Mar 2012 14:05:05 -0800	[thread overview]
Message-ID: <78290424.X7tuqrmkrf@laptop> (raw)

If I have a snapshot and reduce it too far, it still shows as a valid
snap in 'lvs' on the attributes line.


# lvs
  LV           VG      Attr   LSize  Origin       Snap%  Move Log Copy%  
Convert
  OriginVolume MyGroup owi-a- 98.46g
  SnapShot     MyGroup swi-a- 73.28g OriginVolume   0.73


# lvreduce --size 10M MyGroup/SnapShop

# lvs
  /dev/MyGroup/SnapShot: read failed after 0 of 4096 at 105725755392: 
Input/output error
  /dev/MyGroup/SnapShot: read failed after 0 of 4096 at 105725812736: 
Input/output error
  snapshot percentage too large
  dm_report_object: report function failed for field snap_percent
  LV           VG      Attr   LSize  Origin       Snap%  Move Log Copy%  
Convert
  OriginVolume MyGroup owi-a- 98.46g
  SnapShot     MyGroup swi-a- 12.00m OriginVolume



lvs --version
  LVM version:     2.02.88(2) (2011-08-19)
  Library version: 1.02.67 (2011-08-19)
  Driver version:  4.22.0





                 reply	other threads:[~2012-03-04 22:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=78290424.X7tuqrmkrf@laptop \
    --to=benscott@nwlink.com \
    --cc=lvm-devel@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.