From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks
Date: Fri, 20 Apr 2007 18:14:47 -0500 [thread overview]
Message-ID: <46294967.6070601@redhat.com> (raw)
In-Reply-To: <20070420230208.GU5967@schatzie.adilger.int>
Andreas Dilger wrote:
> On Apr 20, 2007 12:10 -0500, Eric Sandeen wrote:
>> If ext3 can do 16T, ext2 probably should be able to as well.
>> There are still "int" block containers in the block allocation path
>> that need to be fixed up.
>
> Yeah, but who wants to do 16TB e2fsck on every boot? I think there
> needs to be some limits imposed for the sake of usability.
I figure this is in the fine tradition of "enough rope to hang oneself"
If you have 16T of filesystem you probably know enough to not hang
yourself this way.
*shrug*
It's a bug, today. If we need another change to limit ext2 to 500G or
something, fine by me. :)
-Eric
next prev parent reply other threads:[~2007-04-20 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 17:10 [PATCH] fix ext2 allocator overflows above 31 bit blocks Eric Sandeen
2007-04-20 23:02 ` Andreas Dilger
2007-04-20 23:14 ` Eric Sandeen [this message]
2007-04-21 0:27 ` Mingming Cao
2007-04-21 0:43 ` Eric Sandeen
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=46294967.6070601@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.