From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Goldwyn Rodrigues <goldwyn_r@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Breaking ext2 file size limit of 2TB
Date: Mon, 28 Jun 2004 11:30:13 +0200 [thread overview]
Message-ID: <20040628093013.GR20632@lug-owl.de> (raw)
In-Reply-To: <1088406721.9804291cgoldwyn_r@myrealbox.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Mon, 2004-06-28 12:42:01 +0530, Goldwyn Rodrigues <goldwyn_r@myrealbox.com>
wrote in message <1088406721.9804291cgoldwyn_r@myrealbox.com>:
> > 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.
> > Sounds like an incompatible extension, so you need to mark it as one:)
>
> I am working on the COMPAT fields now. Most probably, I will be able to give Read only access. I have to study more on this.
Just check if there's any code path that could clear your high-bits of
the block counter.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-28 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 7:12 [PATCH] Breaking ext2 file size limit of 2TB Goldwyn Rodrigues
2004-06-28 9:30 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-26 6:11 Goldwyn Rodrigues
2004-06-26 14:13 ` Jan-Benedict Glaw
2004-06-26 6:09 Goldwyn Rodrigues
2004-06-28 17:53 ` Andreas Dilger
2004-06-25 13:04 Goldwyn Rodrigues
2004-06-25 13:34 ` Jan-Benedict Glaw
2004-06-25 19:12 ` Andreas Dilger
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=20040628093013.GR20632@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=goldwyn_r@myrealbox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox