reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: butdiene <butdiene@yahoo.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 mount options
Date: Mon, 24 Dec 2007 03:38:29 +0300	[thread overview]
Message-ID: <476EFF85.2070002@namesys.com> (raw)
In-Reply-To: <14483298.post@talk.nabble.com>

butdiene wrote:

>right now, I'm using the following setting. mount options are not the same as
>in /proc/mounts, I'm not sure which ones are accepted.
>
>but the system seems to be more responsible now. the  optimal_io_size was
>64KB, seems to be too small.
>
>I reduced the atom_max_size (from 0x2f238 = 784MB) to 0x800= 8MB.
>
>not sure how they would help. I will report later if it really helps.
>
>thanks
>
>mount|grep sda3;cat  /proc/mounts |grep root
>/dev/sda3 on / type reiser4
>(rw,iocharset=utf8,tmgr.atom_max_flushers=0,optimal_io_size=2097152,atom_max_size=0x800,atom_max_age=0x600,atom_max_flushers=0)
>rootfs / rootfs rw 0 0
>/dev/root / reiser4
>  
>
atom_max_size=0x2f238,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10

^^^^^^^^^^^^^^^^^^^^   

You have atom_max_size unchanged.
Please, edit your /etc/fstab and reboot.

Thanks,
Edward.

>0 0
>
>
>Edward Shishkin wrote:
>  
>
>>butdiene wrote:
>>
>>    
>>
>>>Hi,
>>>
>>>I run reiser4 on a laptop. I got serious fsync/flush problem.
>>>
>>>almost randomly, the hard drive would run busy for minutes to dozens of
>>>minutes. while the computer is still responsive during this period, but
>>>firefox would hang until the hard gets idle again.
>>> 
>>>
>>>      
>>>
>>Hm.. firefox is fsync-bound app?
>>
>>    
>>
>>>I guess I can set mount options to improve the situation.
>>> 
>>>
>>>      
>>>
>>That hang can have a complex nature.
>>
>>Well, try to play with the mount option "tmgr.atom_max_size=N",
>>where N is atom size in blocks (by default it is total RAM pages / 4).
>>Look at /proc/mounts to make sure that your changes take effect.
>>
>>If it doesn't help, then let me know.
>>
>>Thanks,
>>Edward.
>>
>>    
>>
>>>Any suggestion is appreciated.
>>>
>>>thanks
>>> 
>>>
>>>      
>>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
>>in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
>>    
>>
>
>  
>


  reply	other threads:[~2007-12-24  0:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23  7:45 reiser4 mount options butdiene
2007-12-23 14:12 ` Edward Shishkin
2007-12-24  0:15   ` butdiene
2007-12-24  0:38     ` Edward Shishkin [this message]
2007-12-24  5:53       ` butdiene
2007-12-24 14:28         ` Edward Shishkin
2007-12-24 17:34           ` Zan Lynx
2007-12-25  4:01             ` butdiene
2007-12-26  0:15               ` butdiene
2007-12-26 14:14                 ` butdiene
2007-12-26 20:35                 ` Edward Shishkin
  -- strict thread matches above, loose matches on Subject: below --
2005-09-19  0:12 Ritesh Raj Sarraf
2005-09-19  0:53 ` michael chang
2005-09-19 14:52 ` Vladimir V. Saveliev

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=476EFF85.2070002@namesys.com \
    --to=edward@namesys.com \
    --cc=butdiene@yahoo.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).