All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Peter <sw98234@hotmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 corruption on initial copy
Date: Sat, 02 Sep 2006 13:27:11 -0500	[thread overview]
Message-ID: <44F9CCFF.5050201@slaphack.com> (raw)
In-Reply-To: <edbm8q$ana$1@sea.gmane.org>

Peter wrote:
> On Fri, 01 Sep 2006 17:35:29 -0500, David Masover wrote:
> 
>> Peter wrote:
>>
>>> 2) I did run badblocks on the dest, and it was clean. 3) I am using the
>>> patch from 2.6.17.3 and in my kernel, I have full preempt and cfq
>>> scheduling.
>> What about the kernel on the livecd?
> 
> 
> Anticipatory
> Voluntary

Yes, that should be fine, but I was wondering if it's the same version, 
if you built it yourself, etc etc.

> Plus, it is smp, so there are some additional options checked. Should I
> have preempt=none with reiser4?

I'm not sure.

  reply	other threads:[~2006-09-02 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 11:02 reiser4 corruption on initial copy Peter
2006-09-01 15:24 ` Peter
2006-09-01 22:35 ` David Masover
2006-09-02 10:26   ` Peter
2006-09-02 18:27     ` David Masover [this message]
2006-09-04 14:32 ` Peter
2006-09-05  9:30   ` Vladimir V. Saveliev
2006-09-05 18:53     ` Peter

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=44F9CCFF.5050201@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sw98234@hotmail.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.