From: Mark Sargent <powderkeg@snow.email.ne.jp>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Resizing LVM Revisited
Date: Fri, 28 Oct 2005 12:15:38 +0900 [thread overview]
Message-ID: <436197DA.800@snow.email.ne.jp> (raw)
In-Reply-To: <71EF4685E87CEDB097D1851A@dhcp-2-206.wgops.com>
Michael Loftis wrote:
> For 2.4 kernels (2.4.20 and later) we've always used ReiserFS and had
> extremely good results with online/hot expansion on top of LVMs. We
> use ext3 for our static os/boot areas but all of our data areas, and
> since we're using debian, that's just /var, and maybe /home, reside on
> LVM + ReiserFS.
>
Hi All,
whilst not a direct solution to my current situation I'll keep your
ideas in mind for future deployment. Cheers.
Mark Sargent.
prev parent reply other threads:[~2005-10-28 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 8:35 [linux-lvm] Resizing LVM Revisited Mark Sargent
2005-10-27 12:21 ` Josef Whiter
2005-10-31 3:03 ` Mark Sargent
2005-10-27 16:13 ` Michael Loftis
2005-10-28 3:15 ` Mark Sargent [this message]
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=436197DA.800@snow.email.ne.jp \
--to=powderkeg@snow.email.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).