All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: "Markus TЖrnqvist" <mjt@nysv.org>,
	reiserfs-list@namesys.com, vs <vs@thebsh.namesys.com>
Subject: Re: On plugins, on-disk formatting and such
Date: Mon, 12 Apr 2004 08:13:20 -0700	[thread overview]
Message-ID: <407AB210.9060305@namesys.com> (raw)
In-Reply-To: <20040412133006.GA1579@backtop.namesys.com>

Alex Zarochentsev wrote:

>
>>   
>>   4.2) What exactly does it mean that CONFIG_REISER4_COPY_ON_CAPTURE
>>        is stabler than before? Is it soon safe to configure in?
>>        Is it possible for me to test it on only one filesystem or
>>        do I risk rootfs (and home directory) stability by trying it
>>        out? If I compile it in, what's the best way of testing it?
>>    
>>
>
>we still see fs errors if COC enable. they are rare now, but COC is not stable
>yet.
>
>  
>
Is Vladimir working on it today?

-- 
Hans


  parent reply	other threads:[~2004-04-12 15:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 10:07 On plugins, on-disk formatting and such mjt
2004-04-12 13:30 ` Alex Zarochentsev
2004-04-12 13:39   ` mjt
2004-04-12 15:13   ` Hans Reiser [this message]
2004-04-12 15:28     ` Vladimir Saveliev
2004-04-12 16:53       ` Reiser4 can't compile glibc Szakacsits Szabolcs
2004-04-13 14:21         ` Vladimir Saveliev
2004-04-13 14:49           ` Szakacsits Szabolcs
2004-04-13 16:34             ` Hans Reiser
2004-04-14  1:54           ` Grant Miner
2004-04-14  8:50             ` mjt
2004-04-12 15:15 ` On plugins, on-disk formatting and such Hans Reiser
2004-04-12 15:33   ` mjt
2004-04-12 18:09     ` Hans Reiser
2004-04-12 16:19 ` Hubert Chan

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=407AB210.9060305@namesys.com \
    --to=reiser@namesys.com \
    --cc=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@thebsh.namesys.com \
    --cc=zam@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.