From: Jonathan Bastien-Filiatrault <joe@x2a.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: tune2fs -I seems dangerous
Date: Thu, 04 Dec 2008 18:14:36 -0500 [thread overview]
Message-ID: <4938645C.5010601@x2a.org> (raw)
In-Reply-To: <49385927.9070003@redhat.com>
Eric Sandeen wrote:
> As a small experiment...
> [snip]
> ... this yields 10031 lines of fsck output, and results in about 38% of
> the files that were on the filesystem going missing.
I have had a similar experience converting from 128 to 256 bytes inodes.
After a while, tune2fs -I would simply stop doing IO and using a lot of
CPU with a few IO bursts every half-hour or so. This is on a recent/fast
x86-64 computer. I had to cancel the thing after leaving it running for
over 24 hours.
>
> I don't have the strong sense that tune2fs -I has been shaken out at
> all; should it be shipping as a useable option?
Maybe add a --accept-consequences-of-shooting-myself-in-the-foot flag ?
Cheers,
Jonathan
next prev parent reply other threads:[~2008-12-04 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 22:26 tune2fs -I seems dangerous Eric Sandeen
2008-12-04 23:14 ` Jonathan Bastien-Filiatrault [this message]
2008-12-05 1:25 ` Theodore Tso
2008-12-05 1:24 ` Theodore Tso
2008-12-05 3:08 ` Eric Sandeen
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=4938645C.5010601@x2a.org \
--to=joe@x2a.org \
--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 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).