From: Eric Sandeen <sandeen@redhat.com>
To: supersud501 <supersud501@yahoo.de>
Cc: Calvin Walton <calvin.walton@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file
Date: Wed, 09 Apr 2008 11:09:18 -0500 [thread overview]
Message-ID: <47FCEA2E.3030302@redhat.com> (raw)
In-Reply-To: <47FCD828.9020204@yahoo.de>
supersud501 wrote:
> Calvin Walton wrote:
>> On Tue, 2008-04-08 at 13:36 -0500, Eric Sandeen wrote:
...
>>> Do you in fact have any very large files on the disk?
>> I'm just curious - if I know for sure that I don't have any huge files
>> on my disk, would I be able to do something like use debugfs to simply
>> clear the flag?
>>
>
> interests mee, too. and how are "huge files" defined? thought they are
> >4gb files?
"large" files are for ei->i_disksize > 0x7fffffffULL, or 2147483647
bytes / 2G. This is just max offset, not block counts; i.e. completely
sparse 2g file will set this flag.
the "huge" sb flag is set if any file has i_blocks > ~0UL, or 2^32
512-byte blocks, or around 2T, but in this case I think sparseness
doesn't count; you have to actually have the blocks allocated.
-Eric
next prev parent reply other threads:[~2008-04-09 16:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 17:58 e2fsck (git) on ext4: unsupported feature(s): huge_file supersud501
2008-04-08 18:36 ` Eric Sandeen
2008-04-08 19:45 ` supersud501
2008-04-08 21:00 ` Theodore Tso
2008-04-09 9:15 ` supersud501
2008-04-09 16:11 ` Theodore Tso
2008-04-09 17:53 ` supersud501
2008-04-09 18:59 ` Theodore Tso
2008-04-09 19:23 ` supersud501
2008-04-09 17:56 ` supersud501
2008-04-09 18:12 ` supersud501
2008-04-09 19:06 ` Theodore Tso
2008-04-09 19:19 ` supersud501
2008-04-09 21:08 ` Theodore Tso
2008-04-11 13:04 ` Theodore Tso
2008-04-11 13:38 ` supersud501
2008-04-09 15:50 ` [E2FSPROGS, PATCH] Add support for the HUGE_FILE feature Theodore Ts'o
2008-04-09 12:54 ` e2fsck (git) on ext4: unsupported feature(s): huge_file Eric Sandeen
2008-04-09 14:45 ` Calvin Walton
2008-04-09 14:52 ` supersud501
2008-04-09 16:09 ` Eric Sandeen [this message]
2008-04-08 18:37 ` Eric Sandeen
2008-04-08 22:40 ` Christian Kujau
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=47FCEA2E.3030302@redhat.com \
--to=sandeen@redhat.com \
--cc=calvin.walton@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=supersud501@yahoo.de \
/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.