All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Briggs <jbriggs@esoft.com>
To: Christian Iversen <chrivers@iversen-net.dk>
Cc: Alexander Zarochentsev <zam@namesys.com>,
	reiserfs-list@namesys.com, Mark F <mfaine@knology.net>,
	Ext3-users@redhat.com
Subject: Re: create very large file system
Date: Thu, 20 Jul 2006 10:22:55 -0600	[thread overview]
Message-ID: <1153412575.9802.7.camel@localhost> (raw)
In-Reply-To: <200607201317.54566.chrivers@iversen-net.dk>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

On Thu, 2006-07-20 at 13:17 +0200, Christian Iversen wrote:
> On Thursday 20 July 2006 08:26, Andreas Dilger wrote:
> > On Jul 19, 2006  16:57 +0400, Alexander Zarochentsev wrote:
> > > On Wednesday 19 July 2006 16:10, Mark F wrote:
> > > > I've tried to create a large 5TB file system using both reiserfs and
> > > > ext3 and both have failed.
> > >
> > > you might need to convert the partition table to GPT format for
> > > supporting 2TB+ partitions.  it can be done by the gnu parted tool.
> >
> > Or, for that matter, don't use a partition table at all, since this
> > adds an unhelpful offset to all the filesystem structures and can
> > hurt performance on RAID where the filesystem is trying to align IO
> > to RAID stripe boundaries.
> 
> Can linux still auto-detect raid volumes if there's no partition table?

You're not supposed to be doing it that way these days.  RAID autodetect
is getting tossed out of the kernel in the future (probably still many
versions away though), and RAID, DM, LVM, and maybe even regular
partition setup is going to be done in initramfs / initrd.

At least, that is what I read.
-- 
Jonathan Briggs <jbriggs@esoft.com>
eSoft, Inc.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-07-20 16:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 12:10 create very large file system Mark F
2006-07-19 12:57 ` Alexander Zarochentsev
2006-07-19 13:24   ` Mark F
2006-07-20  6:26   ` Andreas Dilger
2006-07-20  7:11     ` Clay Barnes
2006-07-20 16:46       ` David Masover
2006-07-20 11:17     ` Christian Iversen
2006-07-20 15:02       ` Andreas Dilger
2006-07-20 16:22       ` Jonathan Briggs [this message]
2006-07-20 16:56         ` Avuton Olrich
2006-07-20 17:32           ` David Masover
2006-07-21 15:37 ` Stephen Tweedie
2006-07-21 15:58   ` Mark F

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=1153412575.9802.7.camel@localhost \
    --to=jbriggs@esoft.com \
    --cc=Ext3-users@redhat.com \
    --cc=chrivers@iversen-net.dk \
    --cc=mfaine@knology.net \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.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.