All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: How to handle >16TB devices on 32 bit hosts ??
Date: Sat, 18 Jul 2009 08:09:33 +0200	[thread overview]
Message-ID: <8763dqwmhu.fsf@basil.nowhere.org> (raw)
In-Reply-To: <19041.4714.686158.130252@notabene.brown> (Neil Brown's message of "Sat, 18 Jul 2009 10:08:10 +1000")

Neil Brown <neilb@suse.de> writes:
>
>  With 2TB drives easily available, more people will probably try
>  building arrays this big and we cannot just assume they will only do
>  it on 64bit hosts.

They should -- no 32bit fsck has any chance running on a 16TB volume.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: How to handle >16TB devices on 32 bit hosts ??
Date: Sat, 18 Jul 2009 08:09:33 +0200	[thread overview]
Message-ID: <8763dqwmhu.fsf@basil.nowhere.org> (raw)
In-Reply-To: <19041.4714.686158.130252@notabene.brown> (Neil Brown's message of "Sat, 18 Jul 2009 10:08:10 +1000")

Neil Brown <neilb@suse.de> writes:
>
>  With 2TB drives easily available, more people will probably try
>  building arrays this big and we cannot just assume they will only do
>  it on 64bit hosts.

They should -- no 32bit fsck has any chance running on a 16TB volume.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2009-07-18  6:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  0:08 How to handle >16TB devices on 32 bit hosts ?? Neil Brown
2009-07-18  4:31 ` Andreas Dilger
2009-07-18  4:31   ` Andreas Dilger
2009-07-18  6:16   ` Andi Kleen
2009-07-18  6:52     ` Andreas Dilger
2009-07-18  7:48       ` Andi Kleen
2009-07-18 13:49         ` Theodore Tso
2009-07-18 14:21           ` Andi Kleen
2009-07-18 14:21           ` Andi Kleen
2009-07-18 14:21             ` Andi Kleen
2009-07-18 14:32             ` Andreas Dilger
2009-07-18 18:19             ` Christoph Hellwig
2009-07-19  0:54             ` Leslie Rhorer
2009-07-19 11:04               ` Christoph Hellwig
2009-07-29 15:07           ` Pavel Machek
2009-07-29 15:07           ` Pavel Machek
2009-07-29 15:07             ` Pavel Machek
2009-07-19  3:44         ` Tapani Tarvainen
2009-07-18  6:09 ` Andi Kleen [this message]
2009-07-18  6:09   ` Andi Kleen
2009-07-22  6:59 ` Andrew Morton
2009-07-22  6:59   ` Andrew Morton
2009-07-22 18:32   ` Andreas Dilger
2009-07-22 18:51     ` Andrew Morton
2009-07-22 18:51       ` Andrew Morton

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=8763dqwmhu.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.