linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Vesa-Pekka Palmu <palmu@aski.hut.fi>
To: ehud@unix.mvs.co.il,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM limits?
Date: Mon, 28 Jan 2008 21:53:37 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801282152350.4629@aski.hut.fi> (raw)
In-Reply-To: <200801281801.m0SI10Xi010185@beta.mvs.co.il>

On Mon, 28 Jan 2008, Ehud Karni wrote:

> On Mon, 28 Jan 2008 11:38:14 Chris Cox wrote:
>>
>> Ok.  But it's really impractical to have large multi-terabyte
>> single filesystem today.  What are you wanting to do?  Ever fsck a
>> 2TB filesystem?  Consider yourself warned.
>
> Just last night I ran fsck on my home 1.5 TB file server (it is software
> RAID-5 - mdadm, built on 7200 RPM, 500GB SATA2 x 4, ext3 without LVM).
> It has went 191 days without fsck so when I booted the machine (I just
> upgraded to 2.6.18-53.1.6.el5) it did the fsck automaticaly.
>
> It took less then 90 minutes.
>

ext3 isn't the best filesystem for large volumes, it's worth considering 
alternatives like jfs.

  parent reply	other threads:[~2008-01-28 19:54 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 [this message]
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
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=Pine.LNX.4.64.0801282152350.4629@aski.hut.fi \
    --to=palmu@aski.hut.fi \
    --cc=ehud@unix.mvs.co.il \
    --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).