From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Manegeability with LVM
Date: Mon Mar 4 18:33:01 2002 [thread overview]
Message-ID: <1015288381.24623.11.camel@UberGeek> (raw)
In-Reply-To: <20020304223441.GA3489@localhost>
XFS does support shriking..but not with LVM.
On Mon, 2002-03-04 at 16:34, José Luis Domingo López wrote:
> On Monday, 04 March 2002, at 23:00:10 +0100,
> Anders Widman wrote:
>
> > As my need for diskspace increases all the time I was thinking of
> > using LVM so I could make use of all diskspace and grow/shrink/replace
> > drives as I need to.
> >
> Take into account that there are filesystem that by design doesn't
> support shrinking of filessytems (e.g. XFS). Some others allow you to
> both grow and shrink filesystems, but sometimes you will have to unmount
> the filesystem before modifying its size.
>
> On the LVM part, it was designed to allow growing and reducing LV sizes
> without being necessary to put your machine in some "maintenance" state.
>
> > The only downside to this is the possibility of massive dataloss if I
> > loose any of the 14 disks (drive fails to spin etc...). Would it be
> > possible to setup up a software redundancy like RAID5 with LVM so I
> > can keep this manageability LVM gives me?
> >
> Remember, nothing except regular _and_ verified backups of your valuable
> data can guarantee that your data will survive a hardware _or_ software
> error. I'm am not sure what I fear most, a damaged disk or a severe
> filesystem corruption. Some RAID levels give you additional hardware
> failure protection, but other levels increase your chances of lossing
> data. LVM can be seen as some sort of linear-RAID, and as such, usually
> increases the probability of a broken disk destroying your data.
>
> In other words, backups are (and will always be) the way to go.
>
> --
> José Luis Domingo López
> Linux Registered User #189436 Debian Linux Woody (Linux
> 2.4.18-rc4aa1)
>
> jdomingo AT internautas DOT org => Spam at your own risk
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com
"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb
next prev parent reply other threads:[~2002-03-04 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 16:00 [linux-lvm] Manegeability with LVM Anders Widman
2002-03-04 16:33 ` José Luis Domingo López
2002-03-04 16:45 ` Anders Widman
2002-03-04 18:33 ` Austin Gonyou [this message]
2002-03-05 4:41 ` Goetz Bock
2002-03-05 5:28 ` Heinz J . Mauelshagen
2002-03-05 8:14 ` Martin K. Petersen
2002-03-05 8:17 ` Patrick Caulfield
2002-03-05 2:29 ` William Blunn
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=1015288381.24623.11.camel@UberGeek \
--to=austin@coremetrics.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.