linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4@vger.kernel.org, Takashi Sato <sho@tnes.nec.co.jp>
Subject: Re: [PATCH] ext4: Support large files
Date: Thu, 11 Oct 2007 11:50:10 +0530	[thread overview]
Message-ID: <470DC09A.8060006@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071011060735.GH8122@schatzie.adilger.int>



Andreas Dilger wrote:
> On Oct 11, 2007  10:41 +0530, Aneesh Kumar K.V wrote:
>> This patch converts ext4_inode i_blocks to represent total
>> blocks occupied by the inode in file system block size.
>> Earlier the variable used to represent this in 512 byte
>> block size. This actually limited the total size of the file.
>>
>> This is enabled only if the incompat feature flag
>> EXT4_FEATURE_INCOMPAT_LARGE_BLOCK is set in super block
>> and the kernel is built with CONFIG_LSF.
> 
> NACK.  This must be an old version of the patch.  The major problem is
> that there is no way to incrementally enable this feature, so as soon
> as some file needs to be larger than 2TB, it means that the i_blocks
> count on EVERY file needs to be updated, or it will be incorrect.
> 
> The updated proposal was to set EXT4_HUGE_FILE_FL on the inodes that
> are using fs-blocksize for i_blocks, and if this flag is not set then
> use 512-byte i_blocks.  This allows the filesystem to be compatible
> unless there really are gigantic files.
> 

So how do we calculate ext4_max_size ? Can we do 

if CONFIG_LSF is set then consider that that i_blocks can be represented 
using file system block size ?

-aneesh

      reply	other threads:[~2007-10-11  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  5:11 [PATCH] ext4: Support large files Aneesh Kumar K.V
2007-10-11  6:07 ` Andreas Dilger
2007-10-11  6:20   ` Aneesh Kumar K.V [this message]

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=470DC09A.8060006@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sho@tnes.nec.co.jp \
    /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).