From: Jan Knutar <jk-lkml@sci.fi>
To: Phil Lougher <phil.lougher@gmail.com>
Cc: John Richard Moser <nigelenki@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: Designing Another File System
Date: Thu, 02 Dec 2004 22:18:53 +0200 [thread overview]
Message-ID: <200412022218.54182.jk-lkml@sci.fi> (raw)
In-Reply-To: <cce9e37e041130112243beb62d@mail.gmail.com>
On Tuesday 30 November 2004 21:22, Phil Lougher wrote:
> I've had people trying to store 500,000 + files in a Squashfs
> directory. Needless to say with the original directory implementation
> this didn't work terribly well...
My old-style newsspool longs for a fast filesystem. Once I did something
stupid, did a backup with mkisofs, and tried a ls -lR on the resulting CD.
After a few hours, I decided that I needed the box to do some work instead
of the 100% uninterruptable sys cpu usage, and rebooted it. I wonder how
long that operation would've taken on isofs :) Mind, the cd drive wasnt really
active during that time, so it wasn't an issue of seek-limited IO blocking
the ide bus.
Tried to store it in a zisofs in later days on more recent kernels for morbid
curiosity, and while it didn't effectively hang the machine anymore, it didn't
work terribly well either...
Currently the thing lives on a Reiser3 partition, previously ext3. They seem
to be about the same speed for this in practice. A "du -sh" takes about 15
minutes to execute, tarring it into a tar.bz2 seems to take about as long as
that, too. Using Theodore Tso's spd_readdir.c, the tar backup case ran in
5 minutes once upon a time. spr_readdir throws segfaults at me now with
2.6 kernels though :-(
next prev parent reply other threads:[~2004-12-02 20:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 4:32 Designing Another File System John Richard Moser
2004-11-30 7:16 ` Bernd Eckenfels
2004-11-30 13:07 ` Helge Hafting
2004-12-01 1:16 ` John Richard Moser
2004-11-30 16:31 ` Alan Cox
2004-11-30 18:28 ` Valdis.Kletnieks
2004-11-30 17:46 ` Alan Cox
2004-11-30 19:00 ` Jan Engelhardt
2004-11-30 19:14 ` Valdis.Kletnieks
2004-11-30 20:22 ` Valdis.Kletnieks
2004-12-02 23:32 ` David Woodhouse
2004-12-01 1:35 ` John Richard Moser
2004-11-30 19:22 ` Phil Lougher
2004-12-01 1:42 ` John Richard Moser
2004-12-01 2:46 ` Phil Lougher
2004-12-01 4:32 ` Bernd Eckenfels
2004-12-01 7:51 ` Phil Lougher
2004-12-01 5:11 ` John Richard Moser
2004-12-02 20:18 ` Jan Knutar [this message]
2004-12-07 2:01 ` Phil Lougher
2004-12-07 2:31 ` John Richard Moser
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=200412022218.54182.jk-lkml@sci.fi \
--to=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
--cc=phil.lougher@gmail.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