From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: tune2fs -I seems dangerous
Date: Thu, 04 Dec 2008 16:26:47 -0600 [thread overview]
Message-ID: <49385927.9070003@redhat.com> (raw)
As a small experiment...
dd if=/dev/zero of=fsfile bs=1M count=16
mkfs.ext4 -F -I 128 fsfile
mkdir -p mnt
mount -o loop fsfile mnt
for I in `seq 1 4096`; do echo $I > mnt/file.$I; done
umount mnt
tune2fs -I 256 fsfile
e2fsck -fy fsfile
... this yields 10031 lines of fsck output, and results in about 38% of
the files that were on the filesystem going missing.
I don't have the strong sense that tune2fs -I has been shaken out at
all; should it be shipping as a useable option?
Thanks,
-Eric
next reply other threads:[~2008-12-04 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 22:26 Eric Sandeen [this message]
2008-12-04 23:14 ` tune2fs -I seems dangerous Jonathan Bastien-Filiatrault
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=49385927.9070003@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).