Red Hat :: Mount The Whole System Into The Ramdisk?
Dec 9, 2009
how could i mount the whole system into the ramdisk?I follow the article "http://www.linuxquestions.org/questions/red-hat-31/building-a-diskless-redhat-enterprise-linux-cluster-765393/",and it works.when i use the "df -h" on the diskless client .I find many system driectory is mountted from image_server.when i stop the connection between img_server and diskless client,the diskless client stop working. my question is how can i mount the whole system into ramdisk.
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13Here's the tutorial:Quote:Originally Posted by leigh123linuxF13 Howto for the rpmfusion nvidia drivers This is a Three-Step Process. If you don't follow all three steps, your install will fail!1. Install the nvidia driver. ( if you have 4Gb of RAM or more you will probably have a PAE kernel [32bit only] so follow the PAE part )For GeForce 6, 7, 8, 9, 200 & 300 series cards
Code: su rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-
There's an entry in /etc/fstab which mounts this automatically. If I interpret that correctly, that's a 224 mbyte ramdisk that is consuming 224 mbytes of system memory whether or not I use it. Is that correct? If so, will anything break if I unmount it and delete it from /etc/fstab? Do programs typically depend on it? I'd like to reclaim the system memory (low DRAM machine) for other uses.
I have built a kernel with a ramdisk(ramdisk.image.gz) included. Also in the kernel command line I specified root=/dev/ram0. I am trying to use this ramdisk to load a loopback file as the root filesystem off a fat partition. This is /sbin/init from the ramdisk.
#!/bin/sh mount -n -t msdos /dev/mmcblk0p1 /mnt losetup /dev/loop0 /mnt/linux/linuxdsk.img mount -t ext2 /dev/loop0 /mnt2
[Code]....
The problem is both umount and blockdev report "device is busy". I want to free up this RAM any suggestions?
I've tried to get an opensuse box I have to share a directory via NFS. I've failed each time, but I thought that the third time, I'd enlist some help from the forums, if I could. how do I know that the nfs server and not the client is the problem? Short answer is: I don't! That's why nfs (and many netwrk problems) are laborious, you're troubleshooting needs to take place at both source and desitination. Next question, what do I have set up so far? Well, I did download the nfs server kernel stuff (two months back) and /etc/init.d/nfsserver start seems to get set up OK. No errors and the daemons nfsd, idmapd, mountd area all running. So, I *think* that part is OK. I have the share set up properly in /etc/exportfs and have "exportfs -r" it.
OK, now onto the trickier stuff: the client and iptables. On the client pinging to the nfserver box is perfect, and I have rpcbind running. the reported error is "mount.nfs: mount system call failed" though from experience nfs errors don't mean a whole lot.However, I will go off and check now and see if I need a mountd running on client-side too.Then there's iptables .... ouch, that could be a long and painful trek. I don't see any specific ports being blocked, and it's the iptables that the default v11.2 opensuse came with. I did turn them off and the problem was the same, so whether wishfl thinking or not, I'm hoping it's not an iptables issue.
I'm using some milters on a Sendmail box that recommends using a RAMdisk [tmpfs] to store temporary files, the performance benefits of which are quite noticeable. However, the problem is if a huge number of messages are all delivered at once this partition can be pushed off the physical memory and into swap. When this happens the performance tanks to about 1/20th to 1/30th of normal.Is there anything I can do to keep a tempfs from being swapped to disk?
Have such a question: how to set ramdisk size? Ramdisk: How do you install and set up Ramdisk under Linux (CentOS, RHEL, Fedora)? | Technology: Learn and Share
Here is some article, but somehow GRUB setting takes no effect, size is still limited to 100MB. I need to get ramdisk with size about 700-1500 MB.
Wine is one of the coolest things I've ever seen, but unfortunately it's still not enough to suit my needs as version 1.38 can't install any of the .NET libraries.
I'm trying to boot windows 7 on virtual box, but it seems to demand quite a bit of memory. The "recommended" amount is 512MB, and upon checking my kernel only has 488MB total ram with not much room to spare:
I've tried giving the virtual machine memory sizes in the area of 192-256MB, but that's way too much and the system locks up and aborts from it. Memory sizes in the area of 128MB is just too small and it throws an error that there just isn't enough ram to boot. So the only thing I can do to make this work is to increase the size of the ramdisk for my host OS so I can give more to the virtual machine (not to mention things like flash animations are horribly slow and I'd like to see them get more fluid).
I see that I have 16 ramdisks available to me:
Code: billy@billy-desktop:~$ ls -l /dev/ram* brw-rw---- 1 root disk 1, 0 2010-02-17 09:54 /dev/ram0 brw-rw---- 1 root disk 1, 1 2010-02-17 09:54 /dev/ram1 brw-rw---- 1 root disk 1, 10 2010-02-17 09:54 /dev/ram10
[Code]....
I looked at some guides here and there, but apparently my setup isn't quite the same. I don't have a menu.lst file in boot/grub, and I don't have a grub.conf file anywhere. So I don't know what file I'm supposed to edit for this.
I am trying to boot a ramdisk and am getting the following error:16384 ram0 (driver?)
16384 ram181 (driver?) No filesystem could mount root, tried:ext2 iso9660. Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (1,0)
This is RHEL5 so input the ramdisk_blocksize into isolinux.cfg: DEFAULT linux LABEL linux KERNEL vmlinuz APPEND initrd=initrd.img root=/dev/ram0 ramdisk_blocksize=1024 ramdisk=2969600 rw init=/etc/rc.d/rc.sysinit
I need to get LILO to boot a ramdisk in which the root file system is on /dev/ramdisk. I have tried many iterations of lilo.conf files. The following is one that I would think would work because it worked under 2.4 kernels:
I created a ram disk with this command: sudo mount -t tmpfs -o size=2048M,nr_inodes=500k,mode=777 tmpfs /var/cache/apt-build/build When I run apt-build, I got an error message that the disk is full (unable to copy file or something). But no disk was full when I checked with 'df'.
we know the maximum of files created from the nr_inodes number? Or is there any other option that determines the max number of files created?
How do I set up a 256mb ramdisk on opensuse 11.3 x86_64 ? - The /boot/grub/menu.lst content reads as:
# Modified by YaST2. Last modification on Mon Aug 30 11:33:28 EST 2010 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader default 0 timeout 8 gfxmenu (hd0,1)/boot/message [Code]....
I updated my netbook to the last incarnation of slackware-current yesterday.
My problem is now, that it is no more able to start the ash shell of the initial ramdisk i am using. The ramdisk was created with the latest version of the mkinitrd script.
The error message is:
Code:
And the error happens when the ash from the initial ramdisk is intended to be started. Simply copying the /lib/libc.so.6 stuff (symlink to the real so and the real so) enables to ash to be started but later cryptsetup fails to load.
The initial ramdisk from mid-January i used before did not have such a problem. What i also see is, that the failing ramdisk has a size of only 16k blocks. The one from mid-January was bigger.
I just performed my very first linux install. I used the Debian 6.0.1a iso. I made it all the way through the installation with no problems whatsoever. I was able to select the version from the grub screen, still everything seemed to be going fine...then it froze. I attached an image of the screen where the system froze:
Its basically the loading screen, times 4! At the top left in case its too hard to read, it says: Loading Linux 2.6.32-5-686, then...Loading initial ramdisk... This sounds all fine and dandy to me but it freezes here. I've tried searching the forums and google for an answer and have come up empty...I'm sure someone has had this problem but it seems to be a tough thing to search for. Would appreciate all the help I can get! Oh and btw, here are the system specs:
circa 2001ish Dell Dimension 4300 P4 1.4ghz 256 ram onboard video etc...
On Debian Etch I used to understand how to change boot kernel parameters with Grub. You could just edit menu.lst.
With the newer Grub in Squeeze I am without a clue! I want to set up a ramdisk, say 128 Megs in size, and add that to my boot parameters so that it is created every time the machine starts. Do I set something in /etc/default/grub ?
So after deciding to upgrade the existing fedora install on my laptop from 11 to 12, I decided to use the preupgrade method. After grappling with the boot space issue by clearing out an old kernel that was deemed safe to remove by the python script on the preconfig wiki page and then using tune2fs, I left the computer to do it's thing, periodically checking back on it. I come back to my computer, and after an apparent restart I see this message spat out at me:
kernel panic - not syncing : VFS : unable to mount root fs on unknown block (0,0) I need this laptop up and running for tomorrow and I would appreciate any help given. I have a Fedora 11 live CD running on the laptop and there seems to be an extra 210 filesystem present with the folders efi, grub, lost+found in there, as well as some config files, elf-memtest86+-400, what seems to be .img file amongst other things. If necessary, I can provide a screenshot.
I have updated using zypper from 11.1 to 11.2. Does this process update the boot/menu.lst file with an entry for the new kernel? Didn't for me.
Any rate, that's not really the problem. I have created a new entry in menu.lst to load the new kernel but I don't have a ramdisk image - all I have is a broken link initrd -> initrd-2.6.31.5-0.1-default
After some hours of googling, I've managed to increase the size of the default ramdisks (/dev/ram0-16) to 1 GiB each, I raided them together with mdadm to try it out, then created a filesyste, mounted it etc etc. No problems. The problem comes when I used gparted to move my windows partition over and in the unallocated space (1 GiB), I created an unformatted partition (/dev/sda2)Now when I try to create the raid array I get the following:
Code: :~$ sudo mdadm --create /dev/md0 -l 1 -n 2 /dev/ram0 /dev/sda2 mdadm: Cannot open /dev/sda2: Device or resource busy
I am trying to use the Linux Ramdisk y machine and followed the instructions oninux/Ramdisk/ramdisk.html to create a 4GB ramdisk (total memory is 8GB, linux 2.6.9)The issue is that it is taking me almost exactly the same time to read a 1GB file from ramdisk as it is from disk. I was expecting it to be atleast twice as fast.Has anyone encountered this before?
Once I've booted my Etch install disc, are there some parameters in configuration files I can edit in the ramdisk filesystem that will allow me to install Squeeze instead? Or, even, paramters I can edit to point at the archive.debian.org repository to install Etch?
Why:
I've got a Sun Ultra10 with IDE drives (hard disk and cd drive) on which I previously had Etch installed. I recently tried to upgrade it to Squeeze, botched the upgrade, and formatted the drive. I'm now trying to install Squeeze from scratch.
When I use the Squeeze disc (debian-6.0.0-sparc-xfce+lxde-CD-1.iso), it cannot detect my IDE drives. I also have the disc I originally used to install Etch, way back when. It will boot and detect the drives, but cannot install because Etch is no longer in the repositories.
I've just installed Debian 6.0.1a on a HP Proliant ML115, the install seemed to go ok. As it began to start up it 'Grub Bootloader' loaded then on the screen after the bootup froze at 'Loading initial ramdisk'
