All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: akpm@zip.com.au
Cc: adilger@clusterfs.com, linux-kernel@vger.kernel.org
Subject: Re: ext2 errors w/2.5.x
Date: Mon, 17 Jun 2002 21:17:02 -0700 (PDT)	[thread overview]
Message-ID: <20020617.211702.83417250.davem@redhat.com> (raw)
In-Reply-To: <3D0EB3F2.C128F97C@zip.com.au>

   From: Andrew Morton <akpm@zip.com.au>
   Date: Mon, 17 Jun 2002 21:15:46 -0700

   Andreas Dilger wrote:
   > On Jun 17, 2002  19:56 -0700, David S. Miller wrote:
   > > EXT2-fs error (device sd(8,17)): ext2_find_entry: zero-length directory entry
   > 
   > This would appear to be from accessing a buffer (page) which has not yet
   > been read from disk.  Otherwise you would have an error from e2fsck also.
   > Andrew has been mucking the most in this area...

   Not that, I hope.  Possibly it's the interaction between
   block_write_full_pages's memset outside i_size, truncate and lookup.
   It took me a ridiculous amount of time to get that "correct", so
   it's a suspicion point.   Or possibly locking between lookup and
   truncate (rmdir) and/or creat.
   
   Dave, I assume this is with 8k pages and 4k blocks?
   
Yes, that is the case here.

   Is it repeatable enough to conduct a little experiment?  Like, lock the page
   in ext2_find_entry?
   
I'll try out your patch and get back to you, thanks.

Franks a lot,
David S. Miller
davem@redhat.com

      reply	other threads:[~2002-06-18  4:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18  2:56 ext2 errors w/2.5.x David S. Miller
2002-06-18  3:25 ` Andreas Dilger
2002-06-18  4:15   ` Andrew Morton
2002-06-18  4:17     ` David S. Miller [this message]

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=20020617.211702.83417250.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=akpm@zip.com.au \
    --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 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.