From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] filesystem does not reflect new LV size
Date: Thu Jun 6 14:09:02 2002 [thread overview]
Message-ID: <ufar8jk6x7v.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: "Vladimir G. Ivanovic"'s message of "Thu, 06 Jun 2002 12:01:53 -0700"
>>>>> "VGI" == Vladimir G Ivanovic <vladimir@acm.org> writes:
VGI> Well, I ran with the bit between my teeth....
I didn't have problems running resize2fs (actually e2fsadm to change
both the LV and filesystem in one go) on plain ext3 without playing
with the journal. You have to unmount it as ext2online doesn't work,
but I was able to grow and shrink an umounted ext3 filesystem
containing data with no problems. Was I just lucky?
- J<
next prev parent reply other threads:[~2002-06-06 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 14:02 [linux-lvm] filesystem does not reflect new LV size Vladimir G. Ivanovic
2002-06-06 14:09 ` Jason L Tibbitts III [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 12:12 Vladimir G. Ivanovic
2002-06-06 12:06 Vladimir G. Ivanovic
2002-06-06 11:39 Vladimir G. Ivanovic
2002-06-06 12:00 ` Joe Thornber
2002-06-06 12:09 ` Tim
2002-06-06 20:16 ` Wolfgang Weisselberg
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=ufar8jk6x7v.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--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