From: Domenico Andreoli <cavok@debian.org>
To: Ciro Mattia Gonano <gonano@CS.UniBO.It>,
"Adam C. Emerson" <adam.emerson@earthlink.net>
Cc: 233219@bugs.debian.org, reiserfs-list@namesys.com
Subject: Re: Bug#233219: reiserfsprogs: fsck fails with "filesystem mounted rw" while filesystem is actually mounted ro
Date: Tue, 17 Feb 2004 20:10:06 +0100 [thread overview]
Message-ID: <20040217191006.GA1384@raptus> (raw)
In-Reply-To: <20040217122723.18F83C2A4@Students.CS.UniBO.It>
[ i'm CCing reiserfs' mailing list ]
hi Ciro and Adam,
this is a known bug that i'm not able to reproduce, indeed i'm able to
check a mounted read-only reiserfs filesystem.
take a look at [0], the thread on upstream's mailing list which
reports same problems. you can find also some tests which could help
understanding what is going wrong here.
please report results and keep all in CC.
many thanks
domenico
[0] http://marc.theaimsgroup.com/?l=reiserfs&m=107651905031144&w=2
On Tue, Feb 17, 2004 at 01:27:23PM +0100, Ciro Mattia Gonano wrote:
> Today I upgraded reiserfsprogs, and at the next reboot I got system
> halts at rcS/checkroot.sh with a failure of fsck.reiserfs that says he
> cannot check a filesystem mounted in read-write, while (as checkroot.sh
> does before) is mounted with
> mount -n -o remount,ro /
> I solved this (temporarily) setting to "no" rootcheck variable in the
> script.
> Any other has experienced this problem?
>
-----[ Domenico Andreoli, aka cavok
--[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
next parent reply other threads:[~2004-02-17 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040217122723.18F83C2A4@Students.CS.UniBO.It>
2004-02-17 19:10 ` Domenico Andreoli [this message]
2004-02-17 19:49 ` Bug#233219: reiserfsprogs: fsck fails with "filesystem mounted rw" while filesystem is actually mounted ro Vitaly Fertman
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=20040217191006.GA1384@raptus \
--to=cavok@debian.org \
--cc=233219@bugs.debian.org \
--cc=adam.emerson@earthlink.net \
--cc=gonano@CS.UniBO.It \
--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.