From: Eric Sandeen <sandeen@redhat.com>
To: supersud501 <supersud501@yahoo.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file
Date: Wed, 09 Apr 2008 07:54:12 -0500 [thread overview]
Message-ID: <47FCBC74.7000500@redhat.com> (raw)
In-Reply-To: <47FBCB44.1050500@yahoo.de>
supersud501 wrote:
> Eric Sandeen wrote:
>> supersud501 wrote:
>>> i get this when trying to run e2fsck on my ext4dev filesystem (kernel
>>> 2.6.25-rc8), extents enabled:
>>>
>>> e2fsck 1.40.8 (13-Mar-2008)
>>> /dev/loop2 has unsupported feature(s): huge_file
>>> e2fsck: Get a newer version of e2fsck!
>>>
>>> just updated to the git-version of e2fsprogs, same error. i know e2fsck
>>> worked once with the drive (~2 months ago).
>>>
>>> what can i do?
>> Do you in fact have any very large files on the disk?
>>
>
> yeah, i have (> 5.5gb).
>
> i know it worked a few months (1-2) ago, even with extents enabled. at
> this time there where those large files too.
For what it's worth, I don't think 5.5gb should have tripped the
huge_file flag. So I wonder how this got set on your fs.
-Eric
next prev parent reply other threads:[~2008-04-09 12:54 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 ` Eric Sandeen [this message]
2008-04-09 14:45 ` e2fsck (git) on ext4: unsupported feature(s): huge_file Calvin Walton
2008-04-09 14:52 ` supersud501
2008-04-09 16:09 ` Eric Sandeen
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=47FCBC74.7000500@redhat.com \
--to=sandeen@redhat.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.