From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] extending a logical volume
Date: Mon Jan 21 15:04:01 2002 [thread overview]
Message-ID: <27800000.1011646909@duke.wrkhors.com> (raw)
In-Reply-To: <E16SlWH-0001gB-00@arwen.dev33.cvf>
> 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.
I'd suggest checking carefully before attempting to extend
a mounted ext3 filesystem. Even if the doc's claim it's
supported you can get into nasty logic races caused by not
wanting to buffer either the journal or cyl groups as they
are written. Theoretically it's all meta-data, but in reality
it takes time to write and failures during that process
can leave buffered cyl group information in core if the
system croaks.
--
Steven Lembark 2930 W. Palmer
Workhorse Computing Chicago, IL 60647
+1 800 762 1582
next prev parent reply other threads:[~2002-01-21 15:04 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
2002-01-21 15:04 ` lembark [this message]
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=27800000.1011646909@duke.wrkhors.com \
--to=lembark@wrkhors.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.