lkml.org 
[lkml]   [2004]   [Jun]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] Breaking ext2 file size limit of 2TB
From
Date
> You're using a reserved field; how do you mean "compatible" in this
> situation? Think of a filesystem with real files > 2TB. How will an
> unpatched ext3fs driver handle those files? You'll only see the <2TB
> content, right?


When I say compatible, I mean the the filesystem need not be formatted. All you need to do patch the kernel, and re-coompile the module/kernel, and remove the old module and insert the new one (if you are using ext3 as a module).

Currently there is a function in ext3_max_size() which limits the file size to 2TB because of the number of blocks, namely i_blocks.


> May an unpatched version under any circumstances clear the high-order
> bits of the newly introduced 64bit integer, just because it doesn't know
> to preserve this reserved field's value?

With an unpatched version you would not be able to create a file greater than 2TB at all and considers that all files are below 2TB.


> Being unfamiliar eith ext3's internals, are there other
> reserved/free-for-future-use fields that don't clash with the HURD?

Andreas has proposed a few fields but I want to make sure that those fields as well are not used.


> Are you proposing a patch like this for ext2, too?
>

Once approved, it can be used for ext2 as well. Converting the current patch for ext2 would be childs play. ext2 and ext3 use almost the same structures (actually from my point of view, exactly the same but am afraid to use the word "exactly").

--
Goldwyn :o)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [W:0.059 / U:0.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site