All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
Date: Tue Oct 30 02:55:02 2001	[thread overview]
Message-ID: <20011030085547.J690@tykepenguin.com> (raw)
In-Reply-To: <000e01c15e63$5e91c7f0$0300000a@pacbell.net>; from e@arix.com on Fri, Oct 26, 2001 at 02:15:41PM -0700

On Fri, Oct 26, 2001 at 02:15:41PM -0700, Erick Calder wrote:
> > What it's warning you about is reducing the size of the LV without first
> changing
> > the size of the filesystem that is using it.
> 
> aha... maybe I could encourage the man page's maintainer to make that point
> a little clearer?

I've added some extra words to the lvreduce man page to help clarify matters,
and make it a little less scary!

 
> > If you are using an ext2 filesystem then you can use the e2fsadm command:
> >
> > # e2fsadm -l -1 /dev/LVM/mp3z
> 
> I performed the above command expecting I would have to do an lvreduce later
> but it <gasp> did it for me...  I haven't done a compare against backups to
> make sure I didn't lose data ok but I still have the problem... here's the
> output (but read beyond):

It'll be fine. e2dsadm does the filesystem AND LV changes in the right order.

> 
> by the time this code is run I've already un-mounted /var/LVM/mp3z and done
> a "vgchange -a n"... so in retrospect I can say that the only thing that has
> changed (I wasn't having these errors before installing LVM) is that I did a
> "pvcreate /dev/hdc"...
> 
> is the info above of any use and is there anything else I can try?

Don't reboot?

I'm out of ideas now, I'll have think....
 

patrick

  reply	other threads:[~2001-10-30  2:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 16:19 [linux-lvm] Remount a LVM Vol after a system crash Christoph Berger
2001-10-16 21:40 ` Heinz J . Mauelshagen
2001-10-17  9:27   ` [linux-lvm] read_intr errors Erick Calder
2001-10-17 14:29     ` Patrick Caulfield
2001-10-17 20:08       ` Erick Calder
2001-10-18  7:42         ` Patrick Caulfield
2001-10-23 23:19           ` Erick Calder
2001-10-24  4:25             ` Patrick Caulfield
2001-10-26  2:13               ` Erick Calder
2001-10-26  3:29                 ` Patrick Caulfield
2001-10-26 16:16                   ` Erick Calder
2001-10-30  2:55                     ` Patrick Caulfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-17 20:21 Karl
2001-10-17 21:20 ` Erick Calder
2001-10-18  0:09   ` Wolfgang Weisselberg
2001-10-17 22:27 Karl
2001-10-24 11:36 Karl

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=20011030085547.J690@tykepenguin.com \
    --to=caulfield@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.