From: Christian Kujau <lists@nerdbynature.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: supersud501 <supersud501@yahoo.de>, linux-ext4@vger.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file
Date: Wed, 9 Apr 2008 00:40:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.10.0804090032480.3869@sheep.housecafe.de> (raw)
In-Reply-To: <47FBBB59.3020506@redhat.com>
On Tue, 8 Apr 2008, Eric Sandeen wrote:
> Oh, and for what it's worth, fsck support for ext4 is incomplete, even
> in git.
"Incomplete", but usable I may add. I've had a few (I/O related) crashes
and ext4 told me that running e2fsck was recommended. I did several times
and it went ok.
> That accounts for lots of the "dev" part in "ext4dev."
Yeah, I won't argue with that statement :)
my 2 cents...
C.
--
BOFH excuse #24:
network packets travelling uphill (use a carrier pigeon)
prev parent reply other threads:[~2008-04-08 22:40 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
2008-04-08 18:37 ` Eric Sandeen
2008-04-08 22:40 ` Christian Kujau [this message]
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=alpine.DEB.1.10.0804090032480.3869@sheep.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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