From: "Vladimir V. Saveliev" <vs@namesys.com>
To: "Frieder Bürzele" <linux-stuff@arcor.de>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.6.14-rc5-mm1/2.6.14-mm1 reiser4-update-for-2.6.14-rc5-mm1-1 still get lockups
Date: Mon, 07 Nov 2005 17:31:38 +0300 [thread overview]
Message-ID: <436F654A.3050705@namesys.com> (raw)
In-Reply-To: <436F58B9.6040105@arcor.de>
Hello
Frieder Bürzele wrote:
> Hi,
>
> i´ve tried the new update-patch reiser4-update-for-2.6.14-rc5-mm1-1 with
> 2.6.14-rc5-mm1/2.6.14-mm but it locks if I run a script that try to
> untar/cp/rm
> stuff on that partition:
>
Does the system lock completely, or processes can not complete?
>
> this messages I got:
>
> <4>reiser4[ktxnmgrd:hda1:r(4321)]: disable_write_barrier
> (fs/reiser4/wander.c:233)[zam-1055]:
> WARNING: disabling write barrier
>
> or this
>
> <4>reiser4[tar(21136)]: disable_write_barrier
> (fs/reiser4/wander.c:233)[zam-1055]:
> WARNING: disabling write barrier
>
these are harmless.
>
> with the reiser4 patch from 20.10.2005 + reiser4-fix-livelock-2.patch +
> reiser4-spinlock-cleanup-2.patch
> all works fine
>
We also have found some problems with this patch. We hope to make a new patch today.
prev parent reply other threads:[~2005-11-07 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 13:38 2.6.14-rc5-mm1/2.6.14-mm1 reiser4-update-for-2.6.14-rc5-mm1-1 still get lockups Frieder Bürzele
2005-11-07 14:31 ` Vladimir V. Saveliev [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=436F654A.3050705@namesys.com \
--to=vs@namesys.com \
--cc=linux-stuff@arcor.de \
--cc=reiserfs-list@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 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.