linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jordi Prats <jprats@cesca.es>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM limits?
Date: Tue, 29 Jan 2008 01:16:20 +0100	[thread overview]
Message-ID: <479E7054.3060901@cesca.es> (raw)
In-Reply-To: <1C8CF1EA1A5B5940B81B0710B2A4C9385030AC683C@an-ex.ActiveNetwerx.int>

Agree. But, at least in my case, I've been studying better alternatives
(this means testing) but I've been required to grow the file system
because of our needs.

So, It's not the best solution, but until I can move to a better one
(this probably means buy more hardware) this is my best option to
provide space.

JFS, XFS and other file systems seems ok, but it wouldn't be a better
solution something like Lustre, Ceph or GlusterFS? They seems to provide
better scalability been also POSIX-compliant. What do you think?

Any inputs will be welcome :)

regards,
Jordi

Joseph L. Casale wrote:
>> It took less then 90 minutes.
>>
>> Ehud.
> 
> 90 Minutes, how "enterprisable" is that? Just cause you can, doesn't mean you should: What if that server tanked during working hours at the corp? You would have to sit and wait for it to come back up. Worse than that are the rebuild times for degraded arrays. Try to rebuild a **huge** array on **huge** discs during production with lots of IO and hope you don't lose another disc. There are practical alternatives with thoughtful management to circumvent the need for and 8EB or larger array, but YMMV :)
> 
> jlc
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
> 

  parent reply	other threads:[~2008-01-28 22:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 10:23 [linux-lvm] LVM limits? Jordi Prats
2008-01-28 19:24 ` Jordi Prats
2008-01-28 17:38   ` Chris Cox
2008-01-28 18:01     ` Ehud Karni
2008-01-28 19:08       ` Chris Cox
2008-01-28 19:53       ` Vesa-Pekka Palmu
2008-01-28 21:52       ` Joseph L. Casale
2008-01-28 23:38         ` Ehud Karni
2008-01-29  0:27           ` Chris Cox
2008-01-29 10:04             ` Ehud Karni
2008-01-29 16:16               ` Chris Cox
2008-01-29  0:16         ` Jordi Prats [this message]
2008-01-28 23:47     ` Jordi Prats
2008-01-29  6:58       ` Michael Eisenkölbl
2008-01-29 17:38       ` Lars Ellenberg
2008-02-01  5:40       ` David Robinson
2008-02-01 13:08         ` [linux-lvm] LVM limits? OT Steeve McCauley

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=479E7054.3060901@cesca.es \
    --to=jprats@cesca.es \
    --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).