public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Alexander Zarochentcev <zam@Namesys.COM>,
	Hans Reiser <reiser@Namesys.COM>,
	lkml <linux-kernel@vger.kernel.org>,
	Oleg Drokin <green@Namesys.COM>, umka <umka@Namesys.COM>
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Mon, 4 Nov 2002 18:10:55 +0100	[thread overview]
Message-ID: <20021104171055.GD8606@louise.pinerecords.com> (raw)
In-Reply-To: <15814.25070.118410.47102@laputa.namesys.com>

>  > Hi,
>  > 
>  > Another one: trying to build 2.5.45 off a reiser4 mountpoint, I get:
>  > 
>  > reiser4[pdflush(7)]: flush_scan_extent (fs/reiser4/flush.c:3127)[nikita-2732]:
>  > WARNING: Flush raced against extent->tail
>  > reiser4[pdflush(7)]: jnode_flush (fs/reiser4/flush.c:1024)[jmacd-16739]:
>  > WARNING: flush failed: -11
>  > jnode_flush failed with err = -11
> 
> Can you please try the following patch to the fs/reiser4/flush.c:
> ----------------------------------------------------------------------
> --- /tmp/flush.c	Mon Nov  4 14:32:21 2002
> +++ flush.c	Mon Nov  4 14:32:32 2002
> @@ -3149,7 +3149,8 @@ flush_scan_extent(flush_scan * scan, int
>  				   only. Will be removed. */
>  				warning("nikita-2732", 
>  					"Flush raced against extent->tail");
> -				ret = -EAGAIN;
> +				scan->stop = 1;
> +				ret = 0;
>  				goto exit;
>  			}
>  			assert("jmacd-1230", item_is_extent(&scan->parent_coord));

Seems to fix the flush errors, however, I can still see the race warnings.
Worse though, at one point I stumbled upon the following:

$ df /ap
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sda2              1490332 -73786976294838198272   1498808 101% /ap

This was right after I hit the reset button while compiling the kernel
off a reiser4 mountpoint, went on to finish the build after reboot and
then "rm -rf"'d the whole source tree (i.e. there was nothing on the
filesystem again).

reiser4.o is 20021031 plus the rmdir leak fix from this thread plus
your patch above.

>  > ... after which r4 crashes completely --
>  > Starts to hog all cpu time and umount() never goes through.
> 
> Try to wait a bit more and check whether any more "WARNING: Too many
> iterations" appear, OK?

Jup, now all I get is the race warnings.

-- 
tomas szepe <szepe@pinerecords.com>

  reply	other threads:[~2002-11-04 17:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 21:23 [BK][PATCH] Reiser4, will double Linux FS performance, please apply Hans Reiser
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:47 ` Hans Reiser
2002-11-01  1:17   ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Andrew Morton
2002-11-01  1:27     ` Andrew Morton
2002-11-05 21:39     ` reiser
2002-11-01  1:27 ` Hans Reiser
2002-11-01  1:33   ` Andrew Morton
2002-11-01  1:44     ` Dieter Nützel
2002-11-01  4:36     ` Linus Torvalds
2002-11-01 10:59       ` Nikita Danilov
2002-11-01  1:55 ` Hans Reiser
2002-11-01 10:23   ` Tomas Szepe
2002-11-01 17:19     ` Alexander Zarochentcev
2002-11-02 13:24       ` Tomas Szepe
2002-11-04 11:00         ` Nikita Danilov
2002-11-04 19:56           ` Andreas Dilger
2002-11-02 13:38       ` Tomas Szepe
2002-11-04 12:02         ` Nikita Danilov
2002-11-04 17:10           ` Tomas Szepe [this message]
2002-11-04 17:53             ` Nikita Danilov
2002-11-04 18:10               ` Tomas Szepe
2002-11-05  7:30 ` reiser
2002-11-05  8:28   ` Alexander Zarochentcev
2002-11-05  9:29   ` Andreas Dilger
2002-11-05  9:59   ` Tomas Szepe
2002-11-05 10:08     ` Alexander Zarochentcev
2002-11-05 10:23       ` Tomas Szepe
2002-11-05 10:46     ` Nikita Danilov
2002-11-05  8:44 ` reiser
2002-11-05  8:49   ` Alexander Zarochentcev
2002-11-05 21:08 ` reiser
     [not found] <877555917@toto.iv>
2002-11-05 23:09 ` Peter Chubb
2002-11-06  1:33   ` reiser
2002-11-06 14:25     ` Daniel Egger
2002-11-07 17:19       ` Pavel Machek
2002-11-07 16:58     ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 18:37 Tom Reinhart

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=20021104171055.GD8606@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=Nikita@Namesys.COM \
    --cc=green@Namesys.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@Namesys.COM \
    --cc=umka@Namesys.COM \
    --cc=zam@Namesys.COM \
    /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