From: "Pysiak Satriani" <pysiak.satriani@wp.pl>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: considerations for reiserfs with lots of files.
Date: Mon, 01 May 2006 14:55:55 +0200 [thread overview]
Message-ID: <4456055bdae5b@wp.pl> (raw)
Hi!
I am running a mail server that stores email on a 270G reiserfs
partition in a Maildir format (one file per email message)
I have an account that is a kind of a tap and receives tremendous
amounts of email. In just over 2 months I have 233k email
messages, ie. 233k files in one directory!
Now, the obvious thing is that accessing that directory takes
some time, I understand that, but I am having other problems with
it. Since creating that account I started having strange problems
like:
- files impossible to delete/read/rename (well actually I found
one like that)
- reiserfsck --fix-fixable told me that it found some nodes that
need --rebuild-tree
- I had an reiserfs related oops, unfortunately It did not save
to the log.
So my question is, are there any special considerations for
reiserfs with huge directories?
I am running 2.6.16.11, the partition is mounted exec,dev,suid,
rw,noatime,notail,iocharset=iso8859-2
It is qmail and courier-imap that operate on these maildir
accounts.
Best regards,
Maciej
reply other threads:[~2006-05-01 12:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4456055bdae5b@wp.pl \
--to=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.