From: Pierrick PONS <ppons@cvf.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] extending a logical volume
Date: Mon Jan 21 14:59:02 2002 [thread overview]
Message-ID: <E16SlWH-0001gB-00@arwen.dev33.cvf> (raw)
In-Reply-To: Your message of "Mon, 21 Jan 2002 12:13:14 PST." <20020121201314.40293.qmail@web20303.mail.yahoo.com>
>
> --- lembark@wrkhors.com wrote:
> >
> >
> > -- Pierrick PONS <ppons@cvf.fr> on 01/21/02 19:09:31
> > +0100
> >
> > > I've read the extending logical volume section and
> > I can't believe this.
> > > According to the doc, it would be impossible to
> > extend a logical volume
>
> um - i think i just did this...
>
> lvextend -L +10G /dev/vg1/data
> followed by
> resize-reiserfs
>
> no corruption (at least not that I've noticed)
>
> maybe i'm misunderstanding...
>
> brad
>
>
I think it's because you're under reiserfs.
I have chosen ext3 file system instead of reiserfs because in case of current
failure some data may have problems if there are data accesses on. That's what
I was said.
Pierrick
next prev parent reply other threads:[~2002-01-21 14:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 12:10 [linux-lvm] extending a logical volume Pierrick PONS
2002-01-21 12:43 ` lembark
2002-01-21 14:13 ` Brad Langhorst
2002-01-21 14:50 ` Harri Haataja
2002-01-21 15:01 ` lembark
2002-01-21 18:47 ` [linux-lvm] Whats wrong with this picture? James Hawtin
2002-01-21 20:37 ` Andreas Dilger
2002-01-22 3:22 ` James Hawtin
2002-01-21 15:22 ` [linux-lvm] extending a logical volume mitch
2002-01-21 15:37 ` Harri Haataja
2002-01-21 18:27 ` James Hawtin
2002-01-21 14:56 ` lembark
2002-01-21 20:40 ` Andreas Dilger
2002-01-21 14:59 ` Pierrick PONS [this message]
2002-01-21 15:04 ` lembark
2002-01-21 20:34 ` Andreas Dilger
2002-01-22 4:37 ` Heinz J . Mauelshagen
2002-01-21 20:29 ` Andreas Dilger
2002-01-22 5:09 ` Pierrick PONS
2002-01-22 6:17 ` James Hawtin
2002-01-22 13:04 ` Andreas Dilger
2002-01-23 9:09 ` Pierrick PONS
2002-01-23 11:40 ` Andreas Dilger
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=E16SlWH-0001gB-00@arwen.dev33.cvf \
--to=ppons@cvf.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox