All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Biscani <biscani@pd.astro.it>
To: reiserfs-list@namesys.com
Cc: Michael Weissenbacher <webmaster@dermichi.com>
Subject: Re: reiser4 corruption problem (maybe related to "Broken reiser4 FS")
Date: Fri, 27 Aug 2004 13:30:32 +0200	[thread overview]
Message-ID: <200408271330.32348.biscani@pd.astro.it> (raw)
In-Reply-To: <412E6EFC.3070600@dermichi.com>

Hi,

On Friday 27 August 2004 01:15, Michael Weissenbacher wrote:
> criminal mnt # uname -a
> Linux criminal 2.6.8.1-mm4 #4 Wed Aug 25 01:34:48 CEST 2004 i686 AMD
> Athlon(tm) XP 2400+ AuthenticAMD GNU/Linux
> the distro is gentoo and i use reiser4progs1.0.1

This may be a long shot, but from the readme on kernel.org it seems that 
2.6.8.1-mm4 could have random breakage:

"- This kernel has an x86 patch which alters the copy_*_user() functions so
  they will return -EFAULT on a fault rather than the number of bytes which
  remain to be copied.  This is a bit of an experiment, because this seems to
  be the preferred API for those functions.   It's a see-what-breaks thing.

  And things will break.  If weird behaviour is observed, please revert
  usercopy-return-EFAULT.patch and send a report."

So maybe you could try 2.6.9-rc1-mm1 amd see if the problem persists. I've 
heard other users having problems with that particular -mm release and 
reiser4.

> thanks,
> michael weissenbacher

Regards,

  Francesco

  reply	other threads:[~2004-08-27 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:15 reiser4 corruption problem (maybe related to "Broken reiser4 FS") Michael Weissenbacher
2004-08-27 11:30 ` Francesco Biscani [this message]
2004-08-27 11:46   ` Michael Weissenbacher
2004-08-28 21:49 ` fsck.reiser4 problem (was: reiser4 corruption problem) Michael Weissenbacher
2004-08-29  6:54   ` Adrian Ulrich
2004-08-29  8:51     ` fsck.reiser4 problem Michael Weissenbacher

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=200408271330.32348.biscani@pd.astro.it \
    --to=biscani@pd.astro.it \
    --cc=reiserfs-list@namesys.com \
    --cc=webmaster@dermichi.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.