From: Andreas Dilger <adilger@Sun.COM>
To: supersud501 <supersud501@yahoo.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck ext4 with extents possible?
Date: Wed, 30 Jan 2008 10:45:35 -0700 [thread overview]
Message-ID: <20080130174535.GF23836@webber.adilger.int> (raw)
In-Reply-To: <47A0574B.1000002@yahoo.de>
On Jan 30, 2008 11:54 +0100, supersud501 wrote:
> i'm testing the ext4-filesystem for months now (no data loss experienced ),
> but i noticed e2fsck not being able to check a ext4-filesystem with extents
> ("e2fsck: Filesystem has unsupported feature(s)").
>
> i just pulled linus' kernel tree (with the newly added patches to ext4) and
> e2fsprogs git tree (from git.kernel.org), but still e2fsprogs is not able
> to check my ext4-fs.
>
> so i wonder whether there's somewhere a patch for e2fsprogs flying around
> i've missed or whether checking ext4 with extents is simply not supported
> yet? if so, how's development going on with this?
There is an e2fsprogs RPM that can check ext4 filesystems with extents,
available at ftp://ftp.lustre.org/pub/lustre/other/e2fsprogs/ (no
warranties, etc). We've been using this for a while already, and are
working to get the patches incorporated into the upstream e2fsprogs
in the interim while Ted is reimplementing the extents support.
Note the above RPMs contain patches which are NOT related just to ext4
and should not become part of a distro.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-01-30 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 10:54 e2fsck ext4 with extents possible? supersud501
2008-01-30 17:31 ` Eric Sandeen
2008-01-30 17:45 ` Andreas Dilger [this message]
2008-01-30 18:14 ` supersud501
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=20080130174535.GF23836@webber.adilger.int \
--to=adilger@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox