From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Max <relf@unn.ac.ru>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
fsdevel <linux-fsdevel@vger.kernel.org>,
Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Re: files of size larger than fs size
Date: Thu, 17 Mar 2005 09:22:35 -0600 [thread overview]
Message-ID: <1111072955.8159.15.camel@localhost> (raw)
In-Reply-To: <42390CFD.3040004@unn.ac.ru>
On Wed, 2005-03-16 at 20:52 -0800, Max wrote:
> Bryan,
>
> I'm not experienced in filesystems. But I've derived the testcase
> program from some buggy application that occasionally created huge
> files on my fs. That was not so easy to reproduce since not every
> sequence of seeks/reads/writes results in a huge file. But finally I
> got it 100% reproducible.
>
> So I would appriciate if somebody make any good from that testcase
> code.
man lseek tells you to test the return code against (off_t)-1. I found
that for larger values, your test program is returning -1, but unsigned
it appears as 18446744073709551615.
>
> Different filesizes look strange to me. What I have so far:
>
> JFS: 281474976706576 = 2**48 - 4080
> XFS: 72057594037923856 = 2**56 - 4080
> EXT3: 1099511627784 = 2**40 + 8
I can speak for jfs, and it supports file sizes up to 2**52. It uses 40
bits to address the logical block offset within a file with a 4K (2**12)
size block. The individual file systems set sb->s_maxbytes to the
appropriate value.
> Thanks,
> Max
>
> P.S. direct link to the testcase program: http://bugzilla.kernel.org/attachment.cgi?id=4729
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2005-03-17 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 2:17 files of size larger than fs size Max
2005-03-16 1:21 ` Phillip Lougher
2005-03-16 2:57 ` Max
2005-03-16 17:05 ` Bryan Henderson
2005-03-17 4:52 ` Max
2005-03-17 15:22 ` Dave Kleikamp [this message]
2005-03-17 20:06 ` Bryan Henderson
2005-03-17 20:51 ` Dave Kleikamp
2005-03-17 21:29 ` Dave Kleikamp
2005-03-17 21:39 ` Dave Kleikamp
2005-03-17 21:48 ` Max
2005-03-17 21:58 ` Dave Kleikamp
2005-03-17 22:25 ` Bryan Henderson
2005-03-16 2:25 ` Sonny Rao
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=1111072955.8159.15.camel@localhost \
--to=shaggy@austin.ibm.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=relf@unn.ac.ru \
/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.