From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: What is status of metadata_csum
Date: Fri, 17 Jan 2014 10:54:46 -0800 [thread overview]
Message-ID: <20140117185446.GB3897@birch.djwong.org> (raw)
In-Reply-To: <52D8E755.6030205@rempel-privat.de>
On Fri, Jan 17, 2014 at 09:18:29AM +0100, Oleksij Rempel wrote:
> Am 17.01.2014 03:00, schrieb Darrick J. Wong:
> > On Thu, Jan 16, 2014 at 11:57:20AM +0100, Oleksij Rempel wrote:
> >> What is metadata_csum status?
> >>
> >> i see there are benchmark updates on wiki page, but no updates for
> >> e2fsprogs. 1.43-WIP seems to be really old.
> >
> > Still waiting for 1.43. I don't know if there are early adopters running
> > 1.43-WIP without complaint, or if simply nobody's using it at all. :/
>
> I didn't tested current master.git - my bad. It is not outdated :)
>
> Beside, the wiki should be corrected. If you enable 64bit, it will need
> extents too.
I updated the howto. mke2fs (as of 1.42.9) should no longer allow
extents,64bit on a filesystem.
--D
>
> Are there any existing tools for error injection for file systems?
> Random read error from libata or silent data corruptions?
> --
> Regards,
> Oleksij
>
prev parent reply other threads:[~2014-01-17 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 10:57 What is status of metadata_csum Oleksij Rempel
2014-01-17 2:00 ` Darrick J. Wong
2014-01-17 8:18 ` Oleksij Rempel
2014-01-17 10:39 ` Oleksij Rempel
2014-01-17 19:21 ` Darrick J. Wong
2014-01-17 20:13 ` Oleksij Rempel
2014-01-17 20:58 ` Darrick J. Wong
2014-01-17 22:32 ` Oleksij Rempel
2014-01-17 18:54 ` Darrick J. Wong [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=20140117185446.GB3897@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux@rempel-privat.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;
as well as URLs for NNTP newsgroup(s).