reiser4 mount options

reiser4 mount options

[Ritesh Raj Sarraf]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello People,

Despite the fact said that reiser4 is not stable so isn't included in
mainline kernel, I trusted Hans Reiser's statement that they've not been
able to crash the fs in the labs.

I just migrated my laptop from plain partitions with ext3 to Reiser4 on LVM.
Till now, I'm pretty happy with the performance.
2.2 gigs of files in ext3 show 1.9 gigs in Reiser4. Thanks to all your work.
Disk access is almost doubled. I haven't measured it, I just feel it.

Thanks to all of you.

Some questions,
What mount options should one use for laptops ? (Right now I'm using
"defaults")
When can we have the reiser4 version of filesystem resize utility ?

Regards,
rrs
- -- 
Ritesh Raj Sarraf
RESEARCHUT -- http://www.researchut.com
Gnupg Key ID: 04F130BC
"Stealing logic from one person is plagiarism, stealing from many is
research."
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDLgKD4Rhi6gTxMLwRAiYJAJ4yFlOCFC3K3vJaafIgSqASW0T/dgCggts4
TGWhaSnYT99Hfigts8au5MY=
=mxiM
-----END PGP SIGNATURE-----

Re: reiser4 mount options

[michael chang]

On 9/18/05, Ritesh Raj Sarraf <riteshsarraf@users.sourceforge.net> wrote:
> When can we have the reiser4 version of filesystem resize utility ?

Namesys/Hans Reiser seem to be waiting for Mainline Kernel inclusion,
since OSes like Ubuntu won't support Reiser4 until it's in the
mainline kernel (among other reasons).

However, becuase of the frequent requests, it seems the
resizer/repacker are high on the list... although they keep saying
it'll come after mainline kernel inclusion.

It's somewhere in the archives, although reading through those is painful.

-- 
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.

Re: reiser4 mount options

[Vladimir V. Saveliev]

Hello

Ritesh Raj Sarraf wrote:
> Hello People,
> 
> Despite the fact said that reiser4 is not stable so isn't included in
> mainline kernel, I trusted Hans Reiser's statement that they've not been
> able to crash the fs in the labs.
> 

Well, there are known ways to crash reiser4 and we are working to fix that. However, my desktop is reiser4 but /boot for more than year already.

> I just migrated my laptop from plain partitions with ext3 to Reiser4 on LVM.
> Till now, I'm pretty happy with the performance.
> 2.2 gigs of files in ext3 show 1.9 gigs in Reiser4. Thanks to all your work.
> Disk access is almost doubled. I haven't measured it, I just feel it.

Remember that it is yet experimental. Backup important things regularly. You have to do that even you used the most reliable fs in the world, though.

> 
> Thanks to all of you.
> 
> Some questions,
> What mount options should one use for laptops ? (Right now I'm using
> "defaults")

There are no one which are designed for laptops. Most of them were created to measure impact of various things on performance and default are set based on some
experemnts with those mount options. On short, there is not need to vary mount options unless you wish to do some experements.

> When can we have the reiser4 version of filesystem resize utility ?
> 

There is no reiser4 resizer yet.

reiser4 mount options

[butdiene]

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.

I guess I can set mount options to improve the situation.

Any suggestion is appreciated.

thanks
-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14476466.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[Edward Shishkin]

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
>  
>

Re: reiser4 mount options

[butdiene]

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
rw,atom_max_size=0x2f238,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10
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
> 
> 

-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14483298.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[Edward Shishkin]

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
>>
>>
>>    
>>
>
>  
>

Re: reiser4 mount options

[butdiene]

I think this is a success report.

with optimal_io_size=2097152,atom_max_size=0x800, reiser4 runs very
reasonable now. I put very heavy load on the file system. In past, those
operations would definitely hang firefox for minutes, but it's barely
noticeable now.

fstab line:
UUID=1b9fdd32-127f-4751-b6aa-5eb300000000 /		reiser4
defaults,iocharset=utf8,optimal_io_size=2097152,atom_max_size=0x800	0 1

cat /proc/mounts:
/dev/root / reiser4
rw,atom_max_size=0x2f238,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10
0 0

/proc/mounts doesn't agree with either fstab or "mount", I don't know why. I
dare not to modify reiser4 source to print out valid settings.

thanks a lot!


output of mount:
/dev/sda3 on / type reiser4
(rw,iocharset=utf8,optimal_io_size=2097152,atom_max_size=0x800)




Edward Shishkin wrote:
> 
> 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
>>>
>>>
>>>    
>>>
>>
>>  
>>
> 
> -
> 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
> 
> 

-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14484849.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[Edward Shishkin]

butdiene wrote:

>I think this is a success report.
>
>with optimal_io_size=2097152,atom_max_size=0x800, reiser4 runs very
>reasonable now. I put very heavy load on the file system. In past, those
>operations would definitely hang firefox for minutes, but it's barely
>noticeable now.
>
>fstab line:
>UUID=1b9fdd32-127f-4751-b6aa-5eb300000000 /		reiser4
>defaults,iocharset=utf8,optimal_io_size=2097152,atom_max_size=0x800	0 1
>
>cat /proc/mounts:
>/dev/root / reiser4
>rw,atom_max_size=0x2f238,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10
>0 0
>
>/proc/mounts doesn't agree with either fstab or "mount", I don't know why. I
>dare not to modify reiser4 source to print out valid settings.
>
>  
>

Valid settings are in /proc/mounts, so we can see, that the problem
still exists..

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.

Thanks,
Edward.

>thanks a lot!
>
>
>output of mount:
>/dev/sda3 on / type reiser4
>(rw,iocharset=utf8,optimal_io_size=2097152,atom_max_size=0x800)
>
>
>
>
>Edward Shishkin wrote:
>  
>
>>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
>>>>
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>> 
>>>
>>>      
>>>
>>-
>>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
>>
>>
>>    
>>
>
>  
>

Re: reiser4 mount options

[Zan Lynx]

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]


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>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: reiser4 mount options

[butdiene]

/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>
> 
>  
> 

-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14493053.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[butdiene]

unfortunately, "sync" still hangs firefox

anything else to try?


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>
>> 
>>  
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14498380.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[butdiene]

I guess the solution for me is atom_min_size=0x100 or even smaller.

for a laptop, I don't want anything to hang, even at cost of general fs
performance.

/dev/root / reiser4
rw,atom_max_size=0x100,atom_max_age=0x927c0,atom_min_size=0x100,atom_max_flushers=0x1,cbk_cache_slots=0x10
0 0



butdiene wrote:
> 
> unfortunately, "sync" still hangs firefox
> 
> anything else to try?
> 
> 
> 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>
>>> 
>>>  
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/reiser4-mount-options-tp14476466p14502529.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.

Re: reiser4 mount options

[Edward Shishkin]

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>
>>>
>>> 
>>>
>>>      
>>>
>>    
>>
>
>  
>