All of lore.kernel.org
 help / color / mirror / Atom feed
From: Basil Chupin <blchupin@tpg.com.au>
To: reiserfs-list@namesys.com
Subject: Re: What does this mean?
Date: Tue, 06 Aug 2002 16:33:31 +1000	[thread overview]
Message-ID: <3D4F6DBB.7030002@tpg.com.au> (raw)
In-Reply-To: 3D2FFA1B.8050302@tpg.com.au

Basil Chupin wrote:

> Valdis.Kletnieks@vt.edu wrote:
>
>> On Fri, 12 Jul 2002 15:48:27 +1000, Basil Chupin said:
>>
>>  
>>
>>> Please let me give a brief resume of why I am trying to find out why 
>>> my HD is being accessed every 5 seconds (actually it is also 
>>> occurring on another computer at home and a friend's machine -- and 
>>> all are running SuSE 8.0).
>>>
>>>  I first asked this Q isn another forum and received the general 
>>> reply that it all had to do with the reiser fs -- which I didn't 
>>> really believe. Why? because I didn't recall having this "problem" 
>>> when I was running SuSE v7.2 with reiser fs. But just to be sure I 
>>> started doing some testing.
>>>
>>> I have another HD which I use for testing purposes and on this one I 
>>> installed SuSE v7.2 undere reiserfs. There was no 5 second accessing 
>>> on the HD.
>>>
>>> I then installed SuSE 8 with ext3 (because someone said that the 5 
>>> seconds-thingie only happened under reiser) - and I still got the 5 
>>> secs access. So, it wasn't confined to reiserfs.
>>>   
>>
>>
>> Note that ext3 *also* has a 'kjournald' that ticks every 5 seconds.
>>  
>>
> Ah, so it has similarities with reiser.
>
>> I'm willing to bet that the system that wasn't seeing the ticking had all
>> the filesystems mounted as ext2, which doesn't have a journal.
>>  
>>
> Had you bet you would have lost! :-). All systems are operating under 
> reiserfs.
>
> You mentioning kjournald brought to min a conversation I had with a 
> friend of mine who tends to have a similar approach to me when 
> starting to run a new system (Linux [SuSE] in this case) and who also 
> uses a second HD to test new installations before putting them onto 
> the 'main' system.
>
> We compared the outputs from the 'ps aux' command and what I found is 
> that I am not running the kjournald process on any of my (3) 'systems' 
> while he is (on his 2 'systems') even though our setups are almost 
> identical (with regards to running SuSE v8 ). I thought kjournald was 
> part and parcel of reiserfs but then why isn't it running on my 
> 'systems'? Just another mystery.
>
> Anyway, I think I have found the reason why I (and my friend and some 
> other(s)) am having the HD accessed every 5 seconds, and after I have 
> re-checked my finding I'll post the reason. It may not have anything 
> directly to do with reiserfs but it may be  that another application 
> may be causing reiserfs to misbehave (in this 5-second syndrome) or, 
> of course, it has a bug in it causing the kernel to do the 'wrong 
> thing' (the application does a patch to the kernel).
>
> Cheers.
>
I apologise for the delay in following-up on this topic but I have been 
occupied on other things (including upgrading my system).

What I found is that, at least in my case (and my friend's), the 
5-second accessing of the HD is caused by Win4Lin. As soon as I/we boot 
into SuSE without the win4lin kernel the accessing stops and the system 
is quiet as a mouse. I am in touch with NeTraverse (Win4Lin) and they 
are investigating this matter.

In a different forum someone mentioned that when he un-installed 
seti-at-home the 5-second accessing on his system stopped - I mention 
this in case this is of interest to anyone.

I did some extensive (for me, that is :-)) testing and found that the 
5-second accessing occurs when either reiser or ext3 file systems are 
installed but the access time "drops" to once every 35 seconds if ext2 
fs is used. Interesting (?).

Cheers.




  parent reply	other threads:[~2002-08-06  6:33 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
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 [this message]
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=3D4F6DBB.7030002@tpg.com.au \
    --to=blchupin@tpg.com.au \
    --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.