All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com, tariq wali <ganaiwali@gmail.com>
Subject: Re: [linux-lvm] lvextend NEVER works but screws up
Date: Tue, 28 Aug 2012 11:09:15 +0200	[thread overview]
Message-ID: <503C8ABB.10401@redhat.com> (raw)
In-Reply-To: <CAGQjrKYUdQ5VL4hw+Oo=pgp4d_a9nsQA60gYHXhwVdWKtpX1qQ@mail.gmail.com>

Dne 27.8.2012 13:46, tariq wali napsal(a):
> Guys , thanks much for your time on the issue, really appreciate it . I had
> tried everything suggested so far (lvresize/extend) updated filesystem
> tools etc
>
> @Stuart D Gathman , YOU ARE THE MAN SIR :) and nailed it down .
>
> I wanted to reproduce the same issue again and i did that not know how
> ignorant I was being ..
>
> # lvextend -L +40G /dev/vg0/bin-logs
>    Extending logical volume bin-logs to 110.00 GB
>    Logical volume bin-logs successfully resized
>
>
> lvs
>    LV       VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
>    bin-logs vg0  -wi-ao *110.00G*
>    data     vg0  -wi-ao 380.00G
>
> resize2fs /dev/vg0/bin-logs
> resize2fs 1.39 (29-May-2006)
> resize2fs: Filesystem has unsupported feature(s) while trying to open
> /dev/vg0/bin-logs
> Couldn't find valid filesystem superblock.
>
> #this is where I would get psyched , i did the same thing to all my ext2/3
> filesystems and have extended file systems online without an issue for
> years ..but did I fforget the file system type this time , yes indeed I for
> got we have started doing ext4 on all our new servers and didn't realise
> ext4 fancies it's own bells and whistles ..
>
> I ran the all new resize4fs as suggested by Stuart , and it made my day in
> fact it made for the whole week's frustration :)
>
> resize4fs /dev/vg0/logs
> resize4fs 1.41.12 (17-May-2010)
> Filesystem at /dev/vg0/logs is mounted on /bin-logs; on-line resizing
> required
> old desc_blocks = 7, new_desc_blocks = 9
> Performing an on-line resize of /dev/vg0/logs to 37408768 (4k) blocks.
>
> The filesystem on /dev/vg0/logs is now 37408768 blocks long.
>
>
> lvs
>    LV   VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
>    data vg0  -wi-ao 350.00G
>    logs vg0  -wi-ao *142.70G *
>
>
> PS: I am raving fan of lvm all over again :)
>
>
> thanks everyone and issue closed !
>

How about checking 'man lvresize'
and using option  '-r'  i.e.:

lvresize -r -L +40G /dev/vg0/bin-logs

That would be time-saver...

Zdenek

  reply	other threads:[~2012-08-28  9:09 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
2012-08-24 11:55       ` Stuart D Gathman
2012-08-27 11:46         ` tariq wali
2012-08-28  9:09           ` Zdenek Kabelac [this message]
     [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=503C8ABB.10401@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=ganaiwali@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.