From: Edward Shishkin <edward@namesys.com>
To: butdiene <butdiene@yahoo.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 mount options
Date: Wed, 26 Dec 2007 23:35:13 +0300 [thread overview]
Message-ID: <4772BB01.1070006@namesys.com> (raw)
In-Reply-To: <14498380.post@talk.nabble.com>
Hello.
butdiene wrote:
>unfortunately, "sync" still hangs firefox
>
>anything else to try?
>
>
Would you please collect and send me
sysrq-t statistics at firefox-hang time?
It can be activated by doing
echo t > /proc/sysrq-trigger
in root console.
Thanks,
Edward.
>
>butdiene wrote:
>
>
>>/dev/root / reiser4
>>rw,atom_max_size=0x800,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10
>>0 0
>>
>>it works without initrd for me. the mount options are set properly in
>>/proc/mounts now.
>>
>>still need to see how it performs
>>
>>thanks a lot!
>>
>>
>>Zan Lynx wrote:
>>
>>
>>>On Mon, 2007-12-24 at 17:28 +0300, Edward Shishkin wrote:
>>>
>>>
>>>
>>>>Sorry, ignore my suggestion about fstab. It is impossible to pass
>>>>reiser4-specific mount options for ''/" via fstab, because all such
>>>>options
>>>>are passed to "/" via remount, but ->remount_fs() super operation is not
>>>>implemented for reiser4.
>>>>
>>>>However, it is possible to pass reiser4-specific mount options for "/"
>>>>via
>>>>boot loader. I have passed a string "rootflags=tmgr.atom_max_size=2048"
>>>>to my grub, and it works for me. Note, that prefix "tmgr." is required
>>>>and
>>>>values should be passed in decimal format.
>>>>
>>>>
>>>Last year when I needed rootflags I found out that they only work if
>>>your distro implements them through an initrd or initramfs. Since most
>>>distros do this it works ok. But my Gentoo system did not use an
>>>initramfs and I could not get rootflags options to work on the kernel
>>>command line.
>>>
>>>So I made my own initramfs with BusyBox and a short script.
>>>--
>>>Zan Lynx <zlynx@acm.org>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
next prev parent reply other threads:[~2007-12-26 20:35 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
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 [this message]
-- 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=4772BB01.1070006@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).