All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Bormuth <ibormuth@efil.de>
To: reiserfs-list@namesys.com
Subject: Re: [patch] reiser4-for-2.6.20
Date: Sat, 10 Feb 2007 16:09:00 +0100	[thread overview]
Message-ID: <20070210150900.GA8973@efil.de> (raw)
In-Reply-To: <8898527.post@talk.nabble.com>

On 2007-02-09 23:26, squadra wrote:
> i m getting lots of errormessages with the 2.6.20 patch, it looks to me like
> they start when i copy files from  a reiser4 partition, to a ext3.

Hi, thanks for your report. 

* Did you use 2.6.19 on that machine before? Any problems with it?
* Do you use reiser4 cryptocmpress?

I'm running two system using my original 2.6.20-patch.
There wasn't a single problem (even under heavy io).

I just created an ext3 partition and filled it up with files from reiser4.
What did you actually do to trigger the errors? Cryptocompress? 


Ingo

-- 
Ingo Bormuth, voicebox & fax: +49-(0)-12125-10226517
public key 86326EC9, http://ibormuth.efil.de/contact


  reply	other threads:[~2007-02-10 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05  3:01 [patch] reiser4-for-2.6.20 Ingo Bormuth
2007-02-10  7:26 ` squadra
2007-02-10 15:09   ` Ingo Bormuth [this message]
2007-02-10 15:47     ` squadra
2007-02-11  3:08       ` Ingo Bormuth

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=20070210150900.GA8973@efil.de \
    --to=ibormuth@efil.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.