All of lore.kernel.org
 help / color / mirror / Atom feed
From: marco <marco@accessplus.com.au>
To: "E.Gryaznova" <grev@namesys.com>
Cc: btinsley <btinsley@gmail.com>, reiserfs-list@namesys.com
Subject: Re: online fsck
Date: Wed, 25 May 2005 09:26:15 +1000	[thread overview]
Message-ID: <4293B817.5030906@accessplus.com.au> (raw)
In-Reply-To: <42930542.1000407@namesys.com>



E.Gryaznova wrote:

> Hello.
> reiserfsck can check reiserfs filesystem mounted read-only.

Running 'fsck.reiserfs --check -y </dev/part>' will do the trick.  The 
equivalent for ext3 and other filesystems is
'fsck -n </dev/part>', the ext3 version detects that it is mounted rw, 
and does a readonly check.

What I wonder is if we can get fsck.reiser[fs,4] to honour option 
processing in a manner more consistant with
the other fscks, so that adding reiserfs to a list of user choosable 
filesystems is not going to cause a nightmare
of an overhead of filesystem detection, command option re-mapping and 
other related headaches.....

>
> Thanks,
> Lena
>
> btinsley wrote:
>
>> Is there or was there a plan to support running reiserfsck on a
>> mounted v3 filesystem (just a check, not a fix or rebuild)? I seem to
>> remember this being mentioned here at some point in time, but I was
>> unable to find it in the mailing list archive.
>>
>> Thanks!
>>
>>
>>  
>>
>
>
>
>
>

-- 
 Marco Grigull  www.accessplus.com.au  AccessPlus Internet Solutions
Ph +61 7 5451 1146  Fax +61 7 5451 1945 Email marco@accessplus.com.au


  reply	other threads:[~2005-05-24 23:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 18:24 online fsck btinsley
2005-05-24 10:43 ` E.Gryaznova
2005-05-24 23:26   ` marco [this message]
2005-05-25  3:02     ` btinsley
2005-05-27  6:15       ` marco
2005-05-27  9:17       ` Philippe Gramoullé
2005-05-27  9:32         ` Yiannis Mavroukakis
2005-05-27 14:12           ` mjt
2005-05-27 22:50           ` David Masover
2005-05-27 23:04             ` btinsley
2005-05-28  7:58     ` Vladimir Saveliev
     [not found] <20040422150042.5b49c6c3.pegasus@nerv.eu.org>
2004-04-22 13:34 ` Chris Mason
2004-04-22 14:24   ` Jure Pečar
2004-04-22 15:24     ` Chris Dukes
2004-04-22 15:45       ` Nikita Danilov
2004-04-22 15:58         ` Marcelo Pacheco
2004-04-22 17:11         ` Chris Dukes
2004-04-22 17:51   ` Hans Reiser
2004-04-22 18:06     ` Chris Mason
2004-04-22 18:14       ` Hans Reiser
2004-04-22 18:15     ` Chris Dukes
2004-04-25 14:10       ` daniel.poelzleithner
2004-04-22 23:20 ` Matthias Andree

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=4293B817.5030906@accessplus.com.au \
    --to=marco@accessplus.com.au \
    --cc=btinsley@gmail.com \
    --cc=grev@namesys.com \
    --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.