Archbang live have the option, i remember the option copy to ram. but i dont know anything else
Closing for necrobump. If you don't know anything, please don't post. And read the forum rules please.
]]>The way to do it is to run your whole FS in initramfs. I'm just wondering how to get persistent writes. Mini_fo to a storage partition perhaps. I'm not sure.
]]>@saten:
the point of it would actually be that you don't have to run something to make it load faster afterwards. i rarely close my browser anyway. neither is it a time issue, since i usually just suspend my laptop to ram, it is merely a cosmetic thing, so when i run something i don't use much it loads fast too. i could of course just do "cat /usr/lib/* /lib/* /bin/* /usr/bin/* > /dev/null" but that seems hackish to me ^^ (and i like to tinker)cheers Barde
So if I can't get any performance improvement, why should I use free ram to mirror some disk i'll rarely use.
I'll test the raid thing on my desktop pc, to check if on the eee pc I see no difference because of the ssd speed in reading.
]]>cheers Barde
]]>does the kernel actually know that all this stuff is actually already in ram and thus there is no need to load it into memory again, or does it still need to "load" it into memory to execute it?
cheers Barde
I don't know much about raid, especially in such an exotic configuration. i'm making the idea that if you have enough ram, when you first run something it will be cached in memory and so you won't get much improvement in speed with the raid solution.
]]>cheers Barde
]]>/dev/md0:
Version : 0.90
Creation Time : Tue Feb 10 23:10:38 2009
Raid Level : raid1
Array Size : 971840 (949.22 MiB 995.16 MB)
Used Dev Size : 971840 (949.22 MiB 995.16 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Mon Feb 16 19:03:38 2009
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : bfe54a7c:90a9441b:4e150285:707779cf
Events : 0.1684
Number Major Minor RaidDevice State
0 1 0 0 active sync /dev/rd/0
1 8 3 1 active sync writemostly /dev/sda3
after some more hacking i got it working as expected (whole /usr is on /dev/sda3 now). i can't notice any performance improvement
]]>saten: what does it say exactly? Once you understand the boot process, it won't be difficult to fix your problem.
sorry i don't remember the exact error. i managed to get something working by mounting only /usr /except /usr/share in raid 0 with ram.
i modified /etc/mdadm.conf accordingly
what i don't understand now is why my ram seems to be unused. when i launch something i see the led of the ssd on, so i believe that reads are actually done on the ssd. i've used your command to build /dev/md0.
Even with the --write-behind related options, performance still seems limited at times.
Installing gnome was taking forever until I just removed the usb drive itself from the array. It was kind of cool to know that I was running entirely in ram.
And before I shutdown, I just had to hot-add the USB drive back in and let it synchronize.
]]>I mention the subject to alert all users since it is a portion of the system being discussed.
I often introduce comments which expand the scope and may seem wrong or out of place but does encourage others to provide better helpful insight into the subject.
I am not always the last word!
Thanks for the responses!
I may be too old for this...83years+.
]]>The number of ramdisks (brd driver) and their size is whatever you say they are, either directly in the kernel's configuration, or as driver/module parameters (brd.rd_nr and brd.rd_size). Also, in case that wasn't clear, you can't make a RAID array with tmpfs/ramfs mounts, since those are blockless (virtual) filesystems; the md driver needs block devices, hence the use of ramdisks (brd driver).
saten: what does it say exactly? Once you understand the boot process, it won't be difficult to fix your problem.
]]>AFAIK ramdisc is limited to one/half of physical memory.
Tmpfs can use all of memory and then use swap.
Just a reminder....
That's if you're using /dev/shm, which is itself a limited-to-half-memory tmpfs. And you can change the limit by modifying your fstab.
]]>Tmpfs can use all of memory and then use swap.
Just a reminder....
]]>