mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: James Lewis Nance <jlnance@intrex.net>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CFT] ext2 directories in pagecache
Date: Wed, 18 Apr 2001 14:01:59 +0100	[thread overview]
Message-ID: <5.0.2.1.2.20010418135757.00ad5680@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20010418084420.A857@bessie.dyndns.org>
In-Reply-To: <Pine.GSO.4.21.0104121217580.19944-100000@weyl.math.psu.edu> <Pine.GSO.4.21.0104121217580.19944-100000@weyl.math.psu.edu>

At 13:44 18/04/2001, James Lewis Nance wrote:
>On Thu, Apr 12, 2001 at 12:33:42PM -0400, Alexander Viro wrote:
> >       Folks, IMO ext2-dir-patch got to the stable stage. Currently
> > it's against 2.4.4-pre2, but it should apply to anything starting with
> > 2.4.2 or so.
>
>Have you had any feedback about this patch?  I applied it last night to
>2.4.3.  It seemed to work.  When I booted my computer this morning fsck
>complained about problems with the directory on one of my ext2 file systems.
>Since fsck does not run on every boot I dont really have a way of knowing if
>this has anything to do with your patch or not.  I'm running the patched
>kernel again right now.  Ill shutdown and force an fsck later today to see
>if anything shows up.

Well, here is some feedback. I have been using this patch for quite a while 
now without any problems what so ever. Including "make -j bzImage" on a 
dual cpu machine and normal use of a productions system. - Frequent crashes 
during ntfs development (and hence frequent reboots + fsck) have not shown 
up any problems in ext2 + this patch, either. - It seems to be stable all 
right on two different PCs (one SMP, celeron and one UP, pentium 133s).

Best regards,

Anton


-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


  parent reply	other threads:[~2001-04-18 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 16:33 Alexander Viro
2001-04-18 12:44 ` James Lewis Nance
2001-04-18 13:08   ` Alexander Viro
2001-04-18 13:01 ` Anton Altaparmakov [this message]
2001-04-23 22:21 ` [PATCH][CFT] (updated) " Alexander Viro
2001-04-28 18:16   ` Alexander Viro
2001-04-19  1:01 [PATCH][CFT] " Daniel Phillips

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=5.0.2.1.2.20010418135757.00ad5680@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=jlnance@intrex.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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®