All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvreduce
Date: Tue, 18 Sep 2001 12:20:18 +0200	[thread overview]
Message-ID: <20010918122018.A28031@sistina.com> (raw)
In-Reply-To: <Pine.A41.4.31.0109180504240.109452-100000@pascal.math.yorku.ca>; from lukacs@mathstat.yorku.ca on Tue, Sep 18, 2001 at 05:09:36AM -0400

G'abor,

the warning lvreduce displays is ment to make the user aware, that the end
of the LV, which could still hold valid data, will be dropped.

BTW: you can avoid the confirmation with "lvreduce -f".

On Tue, Sep 18, 2001 at 05:09:36AM -0400, G'abor Luk'acs wrote:
> Hi,
> 
> 
> I am in the process of installin Linux 8.0, and I have downloaded and
> compiled lvm version 1.0, I patched the kernel, compiled it, etc. So
> everything semes to work, except for one thing: lvreduce somehow damages
> the whole volume group in a way that it becomes inconsistent.

What does vgck tell you about it?

> 
> Everything else seems to work fine, so I really cannot understand why it
> is happening. The whole message of lvreduce seems to be strange a bit:
> 
> when I am redicing an LV when it is enabled then it askes for
> confirmation, but when I disabled it just to see what happens, it wrote me
> that since it is not active I cannot reduce it.
> 
> I am completely aware to the fact that first I have to resize the FS
> inside, but it is not the question, as resize2fs seems to work pefectly
> well.

Alright.

> 
> Somehow my feeling is that something is wroking with the consistency
> checking mechanism.
> 
> I would really apprecaite if you could advise me about it.
> 
> 
> I am looking forward to hearing from you.
> 
> 
> Thanks in advance,
> 
> Gabor Lukacs
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-09-18 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  9:09 [linux-lvm] lvreduce G'abor Luk'acs
2001-09-18 10:20 ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-26 11:37 Bradley M Alexander
2003-06-27  4:41 ` Heinz J . Mauelshagen
2003-06-27  6:28   ` Bradley Alexander
2007-10-22  4:41 Humble Chirammal
2007-10-22  6:14 ` Itamar Reis Peixoto
2007-10-23  0:36 ` Stuart D. Gathman
2007-10-23  1:08   ` Alasdair G Kergon

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=20010918122018.A28031@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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.