From: supersud501 <supersud501@yahoo.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file
Date: Tue, 08 Apr 2008 21:45:08 +0200 [thread overview]
Message-ID: <47FBCB44.1050500@yahoo.de> (raw)
In-Reply-To: <47FBBB13.7060501@redhat.com>
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.
next prev parent reply other threads:[~2008-04-08 20:37 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 [this message]
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
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=47FBCB44.1050500@yahoo.de \
--to=supersud501@yahoo.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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.