From: Chris Mason <mason@suse.com>
To: Xuan Baldauf <xuan--reiserfs@baldauf.org>
Cc: Chris Wedgwood <cw@f00f.org>, David Rees <dbr@spoke.nols.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: [reiserfs-list] Re: Apparent instability of reiserfs on 2.4.1
Date: Wed, 07 Feb 2001 17:13:06 -0500 [thread overview]
Message-ID: <713040000.981583986@tiny> (raw)
In-Reply-To: <3A81C6BF.D892CFE6@baldauf.org>
On Wednesday, February 07, 2001 11:05:51 PM +0100 Xuan Baldauf
<xuan--reiserfs@baldauf.org> wrote:
> Mhhh. It's a busy server from which I am about 700km away. I don't like to
> restart it now. (Especially because it cannot boot from hard disk, only
> from floppy disk, due to bios problems). But I'd be happy if following is
> true:
>
> (1) Enabling "-o notails" is possible at runtime, i.e. "mount / -o
> remount,notails" works and
Nope.
> (2) Notails is compatible with all the tails found on disk (so notails
> only changes the way the disk is written, not the way the disk is read).
>
This part is true.
Honestly, I don't want to do this kind of debugging on a busy server.
Sure, it is completely safe, etc, etc, but ...
We'll get the info elsewhere, leave the busy servers out of it ;-)
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 22:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 12:06 Apparent instability of reiserfs on 2.4.1 Hans Reiser
2001-02-07 15:47 ` Chris Mason
2001-02-07 16:38 ` [reiserfs-list] " David Rees
2001-02-07 16:48 ` Chris Mason
2001-02-08 6:34 ` Daniel Stone
2001-02-10 13:02 ` Chris Wedgwood
2001-02-10 13:05 ` Daniel Stone
2001-02-10 13:08 ` Chris Wedgwood
2001-02-11 7:00 ` Hans Reiser
2001-02-12 0:56 ` Chris Mason
2001-02-12 19:11 ` Marcelo Tosatti
2001-02-12 20:42 ` Hans Reiser
2001-02-12 19:33 ` Marcelo Tosatti
2001-02-12 21:01 ` Hans Reiser
2001-02-12 23:03 ` Chris Mason
2001-02-12 22:39 ` Hans Reiser
2001-02-13 0:18 ` Chris Mason
2001-02-12 22:44 ` Hans Reiser
2001-02-11 6:58 ` Hans Reiser
2001-02-10 14:47 ` Alan Cox
2001-02-10 21:16 ` David Ford
2001-02-11 0:36 ` Andrius Adomaitis
2001-02-11 8:29 ` Hans Reiser
[not found] ` <wvu261oa80.fsf@freeze.oslo.dnmi.no>
2001-02-11 8:59 ` Hans Reiser
2001-02-11 9:52 ` Adrian Phillips
2001-02-11 9:47 ` Hans Reiser
2001-02-11 17:10 ` Alan Cox
2001-02-11 19:56 ` Andi Kleen
2001-02-12 2:17 ` Rogerio Brito
2001-02-12 9:49 ` Andi Kleen
2001-02-12 13:39 ` Henning P. Schmiedehausen
2001-02-11 21:16 ` Hans Reiser
2001-02-12 9:36 ` Alan Cox
2001-02-11 10:53 ` Alan Cox
2001-02-11 8:50 ` Hans Reiser
[not found] ` <3A818619.7C3967BC@baldauf.org>
2001-02-07 17:39 ` Chris Mason
2001-02-07 17:53 ` Xuan Baldauf
2001-02-07 19:14 ` Xuan Baldauf
2001-02-07 21:47 ` Chris Wedgwood
2001-02-07 21:55 ` Chris Mason
2001-02-07 22:05 ` Xuan Baldauf
2001-02-07 22:13 ` Chris Mason [this message]
2001-02-07 18:41 ` Vedran Rodic
2001-02-07 18:45 ` Chris Mason
2001-02-07 19:15 ` Ivan Pulleyn
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=713040000.981583986@tiny \
--to=mason@suse.com \
--cc=cw@f00f.org \
--cc=dbr@spoke.nols.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=xuan--reiserfs@baldauf.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox