From: Alex Tomas <bzzz@tmi.comex.ru>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [RFC] extents support for EXT3
Date: Fri, 29 Aug 2003 20:10:29 +0400 [thread overview]
Message-ID: <m3r834phqi.fsf@bzzz.home.net> (raw)
In-Reply-To: <3F4F76A5.6020000@wmich.edu> (Ed Sweetman's message of "Fri, 29 Aug 2003 11:52:05 -0400")
>>>>> Ed Sweetman (ES) writes:
ES> in the kernels that would boot (for some reason test4's videodev
ES> driver is borked so i used the mm patchset) passed the serio drivers,
ES> init was unable to be found, no matter what even though it mounted the
ES> root fs and the root fs is not as far as i can tell when booting on
ES> older kernels, corrupted. I'm writing now in mozilla from the very
ES> system but with extents turned off. I'm somewhat afraid though that
ES> even though i didn't mount the partitions with the extents option,
ES> that the patch may still be having an adverse effect. Right now
ES> things seem pretty stable but last night apt was hanging while
ES> generating locales reproducably causing the entire kernel to lose the
ES> ability to do anything to the fs. This was all being tested on
ES> test3-mm1. I am aware that mm does have some patches to ext3 that
ES> aren't in the main kernel i believe. perhaps the xattr stuff is
ES> conflicting in some way? I really have no way of testing the linus
ES> tree directly because the drivers i use wont compile.
first of all, once fs gets mounted with extents support any newly created
files/dirs will be stored in extents-format. thus, if you remount that fs
w/o extents support you won't be able to access those files/dirs.
I really propose you don't use extents on a partitions you care about for a while.
ES> All in all though, when it was enabled, i saw really no difference
ES> from when it was not enabled. dbench 16 gave me ~140MB/sec either
ES> way. md5summing large files resulted in equal performance as well. I
ES> got nothing even close to the kind of performance increases you showed
ES> in the first mail.
quite interesting result. could you help me to investigate that?
it would be great to go through following steps:
1) create fresh ext3 fs
2) mount it w/o extents option
3) run dbench 16 for few times (say, 4)
make sure it performs on that filesystem (cd <mntpoint>; dbench -c ... 16)
4) unmount fs
5) recreate that fs
6) mount it with extents option
'EXT3-fs: file extents enabled' should be printed in logs
7) run dbench 16 for few times
8) unmount that fs and take a look in logs, you should see stats info about
extents usage
thank you!
next prev parent reply other threads:[~2003-08-29 16:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 8:22 [RFC] extents support for EXT3 Alex Tomas
2003-08-28 17:22 ` [Ext2-devel] " Mike Fedyk
2003-08-29 5:55 ` Alex Tomas
2003-08-28 18:12 ` Ed Sweetman
2003-08-29 5:59 ` Alex Tomas
2003-08-29 15:28 ` Ed Sweetman
2003-08-29 15:38 ` Alex Tomas
2003-08-29 15:52 ` Ed Sweetman
2003-08-29 16:10 ` Alex Tomas [this message]
2003-08-29 16:16 ` Alex Tomas
2003-08-29 16:20 ` Ed Sweetman
2003-08-29 16:34 ` Alex Tomas
2003-08-29 17:49 ` Ed Sweetman
2003-08-29 18:09 ` Alex Tomas
2003-08-29 19:55 ` Ed Sweetman
2003-08-29 21:39 ` [Ext2-devel] " Mike Fedyk
2003-08-29 22:25 ` Ed Sweetman
2003-08-29 23:17 ` Mike Fedyk
2003-08-31 20:25 ` Eric W. Biederman
2003-08-31 20:37 ` Alex Tomas
2003-09-05 10:06 ` Pavel Machek
2003-09-05 14:55 ` Eric W. Biederman
2003-08-30 9:09 ` Alex Tomas
2003-08-30 8:55 ` Alex Tomas
2003-08-30 10:13 ` Alex Tomas
2003-08-28 22:00 ` Ramón Rey Vicente
2003-08-29 6:04 ` Alex Tomas
2003-08-29 9:55 ` Ramón Rey Vicente
2003-09-06 0:19 ` jw schultz
2003-09-06 6:09 ` Alex Tomas
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=m3r834phqi.fsf@bzzz.home.net \
--to=bzzz@tmi.comex.ru \
--cc=ed.sweetman@wmich.edu \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@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).