mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: Alexander Viro <viro@math.psu.edu>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org,
	ltp-list@lists.sourceforge.net
Subject: Re: fsync02 test hangs 2.5.1-pre3 + patch
Date: Thu, 29 Nov 2001 00:18:59 -0500	[thread overview]
Message-ID: <20011129001859.B17852@earthlink.net> (raw)
In-Reply-To: <20011128220329.A2718@earthlink.net> <Pine.GSO.4.21.0111282303190.9271-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0111282303190.9271-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Wed, Nov 28, 2001 at 11:12:22PM -0500

On Wed, Nov 28, 2001 at 11:12:22PM -0500, Alexander Viro wrote:
> > This was on a reiserfs system, btw.
> 
> Obvious tests:
> 	a) 2.5.1-pre2

2.5.1-pre2 was fine.

> 	b) 2.5.1-pre2 + fs/super.c from 2.5.1-pre3
> 	c) 2.5.1-pre3 + fs/super.c from 2.5.1-pre2
> (fs/super.c changes are independent from everything else).

I'll try option c and let you know what happens.

> Another possibility is silent fs corruption from 2.5.0/2.4.15 - if you
> ran these kernels you really ought to do fsck -f (or whatever is used
> to force recovery of reiserfs).

I did have some nasty errors while running dbench around those kernel versions.
To be safe, I did a cpio backup and re-mkreiserfs'd three filesystems with 2.4.16.
The filesystem that fsync02 hung on was one of the recently rebuilt filesystems.

-- 
Randy Hron


  reply	other threads:[~2001-11-29  6:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29  2:24 rwhron
2001-11-29  2:32 ` Alexander Viro
2001-11-29  3:03   ` rwhron
2001-11-29  4:12     ` Alexander Viro
2001-11-29  5:18       ` rwhron [this message]
2001-11-29  5:48         ` rwhron
2001-11-29  6:04           ` Alexander Viro
2001-11-29  7:05             ` Jens Axboe
2001-11-29  7:17             ` Alexander Viro

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=20011129001859.B17852@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --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®