From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvextend NEVER works but screws up
Date: Fri, 24 Aug 2012 07:32:52 +0100 [thread overview]
Message-ID: <50372014.3000306@abpni.co.uk> (raw)
In-Reply-To: <CAGQjrKbLD0bwedMGQP58BzdyFsnACdXLiziHLbw=tStAhX4BsA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On 23/08/2012 16:18, tariq wali wrote:
> lvresize to extend an lvm ? how
It's the same syntax as lvextend.
>
> also I cant create a new lvm don't have that much space and the to
> extend the new one and it would mean downtime . don't think it's an
> issue with filesystem tools , lvm has NEVER been consistent in my case .
Can you please provide details on why you don't think it's a filesystem
issue? Have you come across other details that lead you to believe this?
These details may help the list in helping you. While I may be over
simplifying things, all LVM is, is a fancy block mapper. Most
complicated things are done by the filesystem on top.
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
next prev parent reply other threads:[~2012-08-24 6:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 10:08 [linux-lvm] lvextend NEVER works but screws up tariq wali
2012-08-23 11:14 ` tariq wali
2012-08-23 14:10 ` Vic
2012-08-23 15:18 ` tariq wali
2012-08-23 15:23 ` Vic
2012-08-24 6:32 ` Jonathan Tripathy [this message]
2012-08-24 11:55 ` Stuart D Gathman
2012-08-27 11:46 ` tariq wali
2012-08-28 9:09 ` Zdenek Kabelac
[not found] ` <CAGQjrKajQYDc48i+FZhB5zUAJKHtMe4FqSgwx8Ed-z7wRuDVQQ@mail.gmail.com>
2012-10-04 6:32 ` tariq wali
2012-10-04 19:59 ` Stuart D Gathman
2012-08-23 14:21 ` flavio-redhat
2012-08-23 16:08 ` Brassow Jonathan
2012-08-23 16:36 ` Bryn M. Reeves
2012-08-23 16:53 ` Stuart D Gathman
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=50372014.3000306@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--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.