All of lore.kernel.org
 help / color / mirror / Atom feed
From: Basil Chupin <blchupin@tpg.com.au>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: What does this mean?
Date: Tue, 09 Jul 2002 02:13:51 +1000	[thread overview]
Message-ID: <3D29BA3F.7010201@tpg.com.au> (raw)
In-Reply-To: 20020708190923.A928@namesys.com

Oleg Drokin wrote:

>Hello!
>
>On Mon, Jul 08, 2002 at 11:30:13PM +1000, Basil Chupin wrote:
>
>  
>
>>I am running SuSE 8 and the HD is being accessed every 5 seconds by 
>>"something". I thought I would just do a quick check of the reiserfs but 
>>    
>>
>
>atime updates and stuff?
>  
>
I really do not know what is causing this every-5-seconds access. This 
is why I am trying to check the integrity of the fs as part of my 
exercise of finding the reason for the access.

>>on executing "reiserfsck --check --logfile check.log  /dev/hda7" this 
>>produces the error message "/dev/hda7 is mounted w/ write permissions, 
>>can not check it." I cannot find this message documented so am wondering 
>>what it means, and what do I need to do in order to be able to check the 
>>integrity of the reiserfs on my sytem. Can anyone please help?
>>    
>>
>You can only check integrity on read-only mounted fs.
>You can only fix stuff on completely unmounted fs.
>
>Bye,
>    Oleg
>
>.
>
Someone else responded to me earlier with the statement to execute 
following: "mount -o remount,rw  /dev/hda7" which I thought had the "rw" 
wrong; but by changing the "rw" to "ro" I then got the error message, 
"mount: / busy".

All this is perplexing me, firstly because I am not tryng to change 
anything- all I am trying to do is to do what the blurb about reiserfs 
says which is "do this to CHECK the fs"; and secondly, how could one 
ever effect any corrections to the fs if it cannot be mounted!?

All too much for a country lad to fathom.

Cheers.




  reply	other threads:[~2002-07-08 16:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 13:30 What does this mean? Basil Chupin
2002-07-08 15:09 ` Oleg Drokin
2002-07-08 16:13   ` Basil Chupin [this message]
2002-07-08 16:27     ` Kuba Ober
2002-07-08 16:28     ` Kuba Ober
2002-07-12  5:48       ` Basil Chupin
2002-07-12 13:26         ` Valdis.Kletnieks
2002-07-13  9:59           ` Basil Chupin
2002-07-14 16:36             ` Valdis.Kletnieks
2002-07-15 13:27               ` Basil Chupin
2002-08-06  6:33             ` Basil Chupin
2002-07-08 18:27     ` Oleg Drokin
2002-07-12  5:52       ` Basil Chupin
  -- strict thread matches above, loose matches on Subject: below --
2002-10-27 21:07 Michael Rosenthal
2002-12-06 18:04 Eric R. Benoit
2002-12-06 22:28 ` Alan Cox
2003-02-27 15:06 Raymond Leach
2003-02-27 15:48 ` Maciej Soltysiak
2003-03-05 17:02   ` Alexander W. Janssen
2003-03-05  4:55 Michael Paul
2003-03-05  6:37 ` Paul Clements
2003-03-19  9:51 What does this mean ? Frederic Gobin
2003-03-19 11:05 ` Raymond Leach
2003-03-19 11:16   ` Frederic Gobin
2005-05-19  6:23 What does this mean? Andrea Parenti
2005-05-19  6:23 ` Mark D. Studebaker
2006-05-16 16:51 what " Steve Iribarne (GMail)
2006-05-16 17:38 ` Walter L. Wimer III
2006-05-16 17:42   ` Walter L. Wimer III
2006-05-16 18:04     ` Steve Iribarne (GMail)

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=3D29BA3F.7010201@tpg.com.au \
    --to=blchupin@tpg.com.au \
    --cc=green@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.