From: Guy Rouillier <guy.rouillier@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Question re: deleting an LV...
Date: Mon, 06 Jan 2014 11:40:34 -0500 [thread overview]
Message-ID: <52CADC82.60607@gmail.com> (raw)
In-Reply-To: <52CAA89E.1000904@libertytrek.org>
On 1/6/2014 7:59 AM, Tanstaafl wrote:
> On 2013-12-30 8:03 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>> Hello,
>>
>> Due to a misunderstanding about how LVM snapshots work when I set up
>> this system, I now need to delete an LV I had created to use for this
>> purpose (I thought I had to pre-create the LV).
>>
>> Currently I have:
>>
>> # lvscan
>> ACTIVE '/dev/vg/tmp' [5.00 GiB] inherit
>> ACTIVE '/dev/vg/log' [5.00 GiB] inherit
>> ACTIVE '/dev/vg/vtmp' [5.00 GiB] inherit
>> ACTIVE '/dev/vg/var' [700.00 GiB] inherit
>> ACTIVE '/dev/vg/snaps' [4.00 GiB] inherit
>>
>> I just need to delete the /dev/vg/snaps LV, so that that 4GB is
>> available for my LVM snapshots.
>>
>> Am I correct that all I have to do is:
>>
>> # umount /dev/vg/snaps
>> # lvremove /dev/vg/snaps
>>
>> Then remove this line from fstab?
>>
>> This would then result in my VG having 4GB available for taking LVM
>> snapshots?
>
> Would appreciate a confirmation that I don't have to do anything else to
> totally eliminate the snaps LV...
>
> I unmounted it, and commented that line in fstab. lvscan still shows the
> same as above, but lvs shows the snaps with a slightly different attribute:
>
> # lvs
> LV VG Attr LSize
> log vg -wi-ao---- 5.00g
> snaps vg -wi-a----- 4.00g
> tmp vg -wi-ao---- 5.00g
> var vg -wi-ao---- 700.00g
> vtmp vg -wi-ao---- 5.00g
>
> So again - is lvremove /dev/vg/snaps the correct way - and the only
> thing I need to do - to remove that LV as if it had never been created?
Yes. This page has a definition of the attributes:
http://man7.org/linux/man-pages/man8/lvs.8.html. "o" in position 6
means device open; since you've unmounted it, it is no longer open.
I learned via this mailing list that lvremove just updates metadata to
make the space available again, but doesn't remove the filesystem in the
LV. So if you were to recreate the exact same LV you just removed, the
filesystem would still be there. My situation was unusual, and you
probably won't encounter this. But if you want to avoid that minor
possibility, use "wipefs -a /dev/vg/snaps" before lvremove.
--
Guy Rouillier
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
next prev parent reply other threads:[~2014-01-06 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 13:03 [linux-lvm] Question re: deleting an LV Tanstaafl
2014-01-06 12:59 ` Tanstaafl
2014-01-06 16:40 ` Guy Rouillier [this message]
2014-01-06 21:10 ` Tanstaafl
2014-01-06 22:49 ` Mauricio Tavares
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=52CADC82.60607@gmail.com \
--to=guy.rouillier@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 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.