mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 03:05:08 +0400	[thread overview]
Message-ID: <20031018030508.4c168433.alex@clusterfs.com> (raw)
In-Reply-To: <3F905D7D.9030602@wmich.edu>

On Fri, 17 Oct 2003 17:22:05 -0400
Ed Sweetman <ed.sweetman@wmich.edu> wrote:

> none of my directories have more than 60 or so entries.  I keep 
> everything very organized on my hdds.  The largest directories would be 
> the ones holding the largest files but that maxes out at around 60 file 
> entries.  i formatted those partitions with a 4KB inode size.

oh. this seems very confusing for me. extents crashed during readdir() syscall.
4k block may contain upto 60 entries with 60chars length. even if your dir was
larger I don't think it was >16k. so, I really do believe all the extents were
placed in inode body (zero tree depth). also, directory grows in linear manner
only. so, this code patch is very very simple and quite good tested. thus it 
really seems like a corruption, not an error in logic. let me cook a patch that
will show more info.  

also, it's very interesting how is it difficult to reproduce on your box?

thanks!

--
with best regards, Alex

  reply	other threads:[~2003-10-17 23:01 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
2003-10-17 21:22             ` Ed Sweetman
2003-10-17 23:05               ` Alex Tomas [this message]
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=20031018030508.4c168433.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®