All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max <relf@unn.ac.ru>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: files of size larger than fs size
Date: Tue, 15 Mar 2005 18:57:40 -0800	[thread overview]
Message-ID: <4237A0A4.9000103@unn.ac.ru> (raw)
In-Reply-To: <42378A0E.90401@lougher.demon.co.uk>

Thanks for the explanation.
I closed my bugreport as INVALID.

But anyway it's ineteresting why the resulting sparse files have different size on different fs?

Max

Phillip Lougher wrote:
> Max wrote:
> 
>> Hello!
>>
>> I've discovered that it is possible to create files of size much 
>> larger than partition size.
>> I thought that this is JFS bug, so I've filed a bugreport against it 
>> at http://bugzilla.kernel.org/show_bug.cgi?id=4345
>> Detailed info and testcase program are provided there.
>>
>> Later I've found that at least XFS and EXT3 filesystems have the same 
>> problem (though the resulting filesize is different for each fs). So 
>> the problem may be not in fs code but in some other piece of kernel.
>>
>> Could kernel gurus please investigate the problem?
>>
> 
> Your test case isn't writing a full file, it is only writing 4 bytes at 
> various offsets (1^32, 1^40, 1^48, 1^56).
> 
> The filesystems you mention support files with "holes" in them, in 
> otherwords they support gaps between data which don't take up any storage.
> 
> Even though your test case is creating a huge file, only a couple of 
> bytes are written, the rest of the huge file doesn't take up any space.
> 
> The behaviour you're seeing isn't a bug...
> 
> Phillip Lougher
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

  reply	other threads:[~2005-03-16  2:57 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 [this message]
2005-03-16 17:05     ` Bryan Henderson
2005-03-17  4:52       ` Max
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=4237A0A4.9000103@unn.ac.ru \
    --to=relf@unn.ac.ru \
    --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.