From: Alex Tomas <alex@clusterfs.com>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EXT3 extents against 2.6.0-test7
Date: Sat, 18 Oct 2003 00:41:52 +0400 [thread overview]
Message-ID: <20031018004152.6aa9e9c3.alex@clusterfs.com> (raw)
In-Reply-To: <3F904D7F.50403@wmich.edu>
On Fri, 17 Oct 2003 16:13:51 -0400
Ed Sweetman <ed.sweetman@wmich.edu> wrote:
> How am i supposed to know which directory in the fs this corruption
> takes place in? I can tell you the size of the partitions that have
> extents enabled, From that error message i dont even know which
> partition it was. And judging by the dmesg last modified time, this
> happened 2 days ago
OK. the question wasn't clear.
1) could you _estimate_ max directory size or number of entries in single
directory on your filesystems, please? had you large directories?
100, 300, 500 or more entries?
2) did you use 2.6.0-test7+extents or some another patches?
3) could you describe workload. knowing it I'd try to reproduce this
> Isn't it possible though that this happened in one of the non-extents
> enabled partitions though? Since they still have the ability to read
> extents in files, they have to try and look them up every time for
> everything dont they? Anyways, the two partitions above are the only
> ones i actually enable extents on.
>
extents take place only if flag in inode->i_flags is set. that flag can
be set only during inode creation on extents-enabled filesystem.
with best wishes, Alex
next prev parent reply other threads:[~2003-10-17 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 18:27 Alex Tomas
2003-10-13 21:39 ` Ed Sweetman
[not found] ` <20031014212359.42243025.alex@clusterfs.com>
2003-10-17 19:32 ` Ed Sweetman
2003-10-17 20:10 ` Alex Tomas
2003-10-17 20:13 ` Ed Sweetman
2003-10-17 20:41 ` Alex Tomas [this message]
2003-10-17 21:22 ` Ed Sweetman
2003-10-17 23:05 ` Alex Tomas
2003-10-18 0:07 ` Ed Sweetman
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=20031018004152.6aa9e9c3.alex@clusterfs.com \
--to=alex@clusterfs.com \
--cc=ed.sweetman@wmich.edu \
--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
all inboxes | Powered by JetHome®