All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <lvm@tlinx.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lsm space giveth and space taketh away: missing space?
Date: Wed, 01 Sep 2010 18:50:42 -0700	[thread overview]
Message-ID: <4C7F02F2.3040500@tlinx.org> (raw)

I'm running low on space in my /backups partition.  I looked at the
partitions and volumes to see what might be done (besides deleting old
backups), and noticed:

pvs:
  PV         VG         Fmt  Attr PSize  PFree
  /dev/sdb1  Backups    lvm2 a-   10.91T  3.15G

---
So I thought 'cool', I didn't make it the full size, and
I have some left...ok...(I didn't remember what I'd done, its
been a while).

Run lvresize:
lvresize /dev/Backups/Backups -L +3.15G
  Rounding up size to full physical extent 3.15 GB
  Extending logical volume Backups to 10.91 TB
  Logical volume Backups successfully resized

Um...HELLO?  Extending to 10.91?  But it was at 10.91!
pvs:
  PV         VG         Fmt  Attr PSize  PFree
  /dev/sdb1  Backups    lvm2 a-   10.91T     0

Well that was unimpressive.

parted /dev/sdb
p(rint)
Disk /dev/sdb: 12.0TB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name    Flags
 1      17.4kB  12.0TB  12.0TB               backup  lvm






Ok, now I'm really confused.  10.91T?  14.06T?  (Obviously
this was optimistic reporting if the partition is only 12TB!)

So why does parted show a 12TB disk while lvm shows only a 10.91T
disk and why did lvm show 3.15G free when it wasn't really there?

How do I get my 1.09T back from lvm?  That seems like awfully
high for an overhead number for lvm.  I'd expect more like "0.09T".


Ideas?
Linda

             reply	other threads:[~2010-09-02  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02  1:50 Linda A. Walsh [this message]
2010-09-02  3:44 ` [linux-lvm] lsm space giveth and space taketh away: missing space? Stuart D. Gathman
2010-09-02  3:52   ` Stuart D. Gathman
2010-09-02 10:01 ` Bryn M. Reeves
2010-09-02 17:32   ` Linda A. Walsh

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=4C7F02F2.3040500@tlinx.org \
    --to=lvm@tlinx.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.