All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max <relf@unn.ac.ru>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org,
	Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Re: files of size larger than fs size
Date: Wed, 16 Mar 2005 20:52:13 -0800	[thread overview]
Message-ID: <42390CFD.3040004@unn.ac.ru> (raw)
In-Reply-To: <OFEE9E49FC.593522D9-ON88256FC6.005C15F1-88256FC6.005DD9B9@us.ibm.com>

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.

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

Thanks,
Max

P.S. direct link to the testcase program: http://bugzilla.kernel.org/attachment.cgi?id=4729

Bryan Henderson wrote:
>>But anyway it's interesting why the resulting sparse 
>>files have different size on different fs?
> 
> 
> That looks like a bug.  Assuming you didn't see any seeks or writes fail, 
> the file size on all filesystems should be 2^56 + 4.  I suspect this is 
> beyond the maximum file size allowed by the filesystem in some cases, so 
> the write isn't happening, which means you should get a failure return 
> code.
> 
> In the results you showed, the filesize ends up being a little less than 
> 2^48, which is not a place that you wrote ever.
> 
> --
> Bryan Henderson                          IBM Almaden Research Center
> San Jose CA                              Filesystems
> 
> 

  reply	other threads:[~2005-03-17  4:53 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 [this message]
2005-03-17 15:22         ` Dave Kleikamp
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=42390CFD.3040004@unn.ac.ru \
    --to=relf@unn.ac.ru \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    /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.