From: Tracy R Reed <treed@copilotconsulting.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvscan showing 0 free on all PV's.
Date: Wed Sep 17 07:07:04 2003 [thread overview]
Message-ID: <20030916143432.H27659@copilotconsulting.com> (raw)
In-Reply-To: <3F675CDB.80002@tupshin.com>; from tupshin@tupshin.com on Tue, Sep 16, 2003 at 11:56:27AM -0700
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Tue, Sep 16, 2003 at 11:56:27AM -0700, Tupshin Harper spake thusly:
> ext2resize to shrink it, followed by an lvreduce to reduce the size of
> the partition that the filesystem lives on, but *DANGER* *DANGER*
> *DANGER*. Reducing the size of an existing filesystem is inherently
> dangerous, so back up, tread with caution, and don't blame me when a
> meteorite flattens your house.
Inherently dangerous? Nonsense. It should not be inherently dangerous if
the resize tool and LVM do their jobs properly. Resizing should be a
perfectly safe operation when done properly.
> If you are using reiserfs, jfs, or xfs, you are probably out of luck, as
> these filesystems don't currently support reduction.
reiserfs supports reduction. I have done it many times. I wouldn't be
surprised if the others do too but I haven't used them yet.
--
Tracy Reed
http://copilotconsulting.com
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-09-17 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 13:19 [linux-lvm] pvscan showing 0 free on all PV's Rene Olsen
2003-09-16 13:57 ` Tupshin Harper
2003-09-17 1:54 ` Rickard Olsson
2003-09-17 2:02 ` Tupshin Harper
2003-09-17 7:07 ` Tracy R Reed [this message]
2003-09-18 0:29 ` Rickard Olsson
-- strict thread matches above, loose matches on Subject: below --
2003-09-17 7:07 Rene Olsen
2003-09-17 13:57 ` Tupshin Harper
2003-09-19 5:46 ` Heinz J . Mauelshagen
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=20030916143432.H27659@copilotconsulting.com \
--to=treed@copilotconsulting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox