All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fionn Behrens <fionn@spamfilter.de>
To: reiserfs-list@namesys.com
Subject: reiser4 in 2.6.14 - lockups with mmapped files
Date: Tue, 01 Nov 2005 16:50:21 +0100	[thread overview]
Message-ID: <1130860221.12859.23.camel@laptop> (raw)

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]


Hi all,

you may remember my recent "story from userland". Stubborn as I am, I
decided to give 2.6.14 another shot for it. Following a recommendation
found in the above mentioned thread, I tried the patch from 
http://iphitus.loudas.com/archck.php this time, which includes the
latest reiser4 from mm.

Unfortunately I once more hit the wall and was forced to go back to
2.6.11 (including another --build-fs run to regain compatibility with
the old but working reiser4 drivers). I wish there was a mount option to
exclude the new extensions so I can test new kernels without losing half
a day for fscking when things get whacky.

This time suspend seemingly works without reiser4 processes freaking
out.
But now it looks like any time any mmapped file is synced to a reiser4
partition, the process who tries to do that will freeze forever. In
addition, any process trying to access the open mmapped file afterwards
will freeze forever as well. I created a screenshot of an strace running
while this happened. Find it at http://fionn.de/reiser4again.jpg

Of course, tests on files on other file systems than reiser4 did not
show this behaviour. I tested on two different Systems, one Pentium M
and one Athlon, same result.

I wish I knew what I am doing wrong. I'd bet you guys all have reiser4
up and running with 2.6.14 and no problems at all. Or what? 

best regards,
		Fionn
-- 
 Taking away civil rights to protect a free democracy is like taking off
 the tires of a car to protect it from flats. 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-11-01 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 15:50 Fionn Behrens [this message]
2005-11-01 16:25 ` reiser4 in 2.6.14 - lockups with mmapped files Vladimir V. Saveliev
2005-11-01 17:41   ` Fionn Behrens
2005-11-01 19:37     ` Sander
2005-11-03 14:30   ` Fionn Behrens
2005-11-03 15:21     ` Vladimir V. Saveliev
2005-11-03 20:17     ` jp
2005-11-04 16:19       ` Vladimir V. Saveliev
2005-11-04 19:38         ` jp
2005-11-12  1:58           ` rvalles
     [not found]           ` <20051112015840.GA28777@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-12 15:13             ` Artur Makówka
2005-11-15  8:12             ` Vladimir V. Saveliev
2005-11-04 21:12 ` SOLVED: " Fionn Behrens
2005-11-09  0:21   ` rvalles
     [not found]   ` <20051109002158.GA21403@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-09  8:25     ` Raymond A. Meijer

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=1130860221.12859.23.camel@laptop \
    --to=fionn@spamfilter.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.