From: Oleg Drokin <green@namesys.com>
To: "David R. Bergstein" <dbergstein@comcast.net>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: reiserfsck question - session results
Date: Mon, 29 Jul 2002 15:25:56 +0400 [thread overview]
Message-ID: <20020729152556.A1131@namesys.com> (raw)
In-Reply-To: <IMELKMOINBOOFMGACNMDOEFHCLAA.dbergstein@comcast.net>
Hello!
On Mon, Jul 29, 2002 at 07:20:45AM -0400, David R. Bergstein wrote:
> Thanks very much for this information. I sounds like what I did overall
> suppressed several harnless messages, i.e., by mounting the root reiserfs
> read-write, and skipping fsck in the initscripts. From what you are saying,
> journal replay can also work safely when even a reiserfs fs is mounted
> read-only. Is the warning message about journal replay on read-only
> filesystems outdated and if so, will it be removed sometime in the near
> future?
Yes, the warning will be removed. Actually it is just informational message,
just badly phrased.
Bye,
Oleg
prev parent reply other threads:[~2002-07-29 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 3:13 reiserfsck question - session results David R. Bergstein
2002-07-29 4:43 ` David R. Bergstein
2002-07-29 6:00 ` Oleg Drokin
2002-07-29 11:20 ` David R. Bergstein
2002-07-29 11:25 ` Oleg Drokin [this message]
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=20020729152556.A1131@namesys.com \
--to=green@namesys.com \
--cc=dbergstein@comcast.net \
--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.