From: <mar...@gm...> - 2005-08-10 13:33:40
|
Hi UML users! Here is my problem: im using UML, inside my gentoo distro. Made de root_fs from a stage3. Have everything compiled and correctly configured (i think :) but when u try to run "linux", it starts booting but than gives me a erro: * Mounting proc at /proc ... =20 =20 [ ok ] * Mounting sysfs at /sys ... =20 =20 [ ok ] * Mounting /dev for udev ... =20 =20 [ ok ] * Configuring system to use udev ... * Populating /dev with device nodes ... [ oops ] * The "tar" command failed with error: rd/c6d27p4: Cannot mknod: No space left on device tar: rd/c6d27p5: Cannot mknod: No space left on device tar: rd/c6d27p6: Cannot mknod: No space left on device tar: rd/c6d27p7: Cannot mknod: No space left on device tar: rd/c6d28p1: Cannot mknod: No space left on device tar: rd/c6d28p2: Cannot mknod: No space left on device tar: rd/c6d28p3: Cannot mknod: No space left on device tar: rd/c6d28p4: Cannot mknod: No space left on device ... ...... so on so on...... What seems to be the problem? Any ideas? Thanks in advance... --=20 Marco Garc=EAs http:\\dbugs.org mar...@gm... |
From: Nelson C. <nel...@gm...> - 2005-08-10 17:32:32
|
> [ oops ] >=20 > * The "tar" command failed with error: >=20 > rd/c6d27p4: Cannot mknod: No space left on device > tar: rd/c6d27p5: Cannot mknod: No space left on device > tar: rd/c6d27p6: Cannot mknod: No space left on device > tar: rd/c6d27p7: Cannot mknod: No space left on device > tar: rd/c6d28p1: Cannot mknod: No space left on device > tar: rd/c6d28p2: Cannot mknod: No space left on device > tar: rd/c6d28p3: Cannot mknod: No space left on device > tar: rd/c6d28p4: Cannot mknod: No space left on device > ... > ...... > so on so on...... >=20 > What seems to be the problem? Any ideas? Thanks in advance... Is your root_fs full? Mount it with -o loop as root and run df to check. Regards, Nelson.- --=20 Homepage : http://geocities.com/arhuaco The first principle is that you must not fool yourself and you are the easiest person to fool. -- Richard Feynman. |
From: <mar...@gm...> - 2005-08-11 12:45:55
|
On 8/10/05, Nelson Castillo <nel...@gm...> wrote: > > [ oops ] > > > > * The "tar" command failed with error: > > > > rd/c6d27p4: Cannot mknod: No space left on device > > tar: rd/c6d27p5: Cannot mknod: No space left on device > > tar: rd/c6d27p6: Cannot mknod: No space left on device > > tar: rd/c6d27p7: Cannot mknod: No space left on device > > tar: rd/c6d28p1: Cannot mknod: No space left on device > > tar: rd/c6d28p2: Cannot mknod: No space left on device > > tar: rd/c6d28p3: Cannot mknod: No space left on device > > tar: rd/c6d28p4: Cannot mknod: No space left on device > > ... > > ...... > > so on so on...... > > > > What seems to be the problem? Any ideas? Thanks in advance... >=20 > Is your root_fs full? >=20 > Mount it with -o loop as root and run df to check. >=20 > Regards, > Nelson.- >=20 > -- > Homepage : http://geocities.com/arhuaco >=20 > The first principle is that you must not fool yourself > and you are the easiest person to fool. > -- Richard Feynman. >=20 No, the root_fs has enough space.... i know 4 sure! :( any more ideas? --=20 Marco Garc=EAs http:\\dbugs.org mar...@gm... |
From: Ruaidhri P. <rua...@ne...> - 2005-08-11 12:59:43
|
On Thu, Aug 11, 2005 at 12:45:20PM +0000, Marco Garcs wrote: > No, the root_fs has enough space.... i know 4 sure! :( any more > ideas? Could the filesystem have run out of inodes? Use `df -i' to check. -- Ruaidhri |
From: <mar...@gm...> - 2005-08-11 15:02:51
|
---------- Forwarded message ---------- From: Ruaidhri Power <rua...@ne...> Date: Aug 11, 2005 12:59 PM Subject: Re: [uml-user] booting To: use...@li... On Thu, Aug 11, 2005 at 12:45:20PM +0000, Marco Garcs wrote: > No, the root_fs has enough space.... i know 4 sure! :( any more > ideas? Could the filesystem have run out of inodes? Use `df -i' to check. -- Ruaidhri ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -------------------------------- Nope.. left the root_fs mounted on loop, and did a watch "df -i", and this is what i see: /uml/root_fs 0 0 0 - /uml/loop Tryed to boot again, and still no sucess, same error messages, ends up with= : * Since this is a critical task, startup cannot continue. Give root password for maintenance (or type Control-D to continue): -- And the saga continues... tanx for your help :) |
From: Ruaidhri P. <rua...@ne...> - 2005-08-11 15:20:50
|
On Thu, Aug 11, 2005 at 03:02:44PM +0000, Marco Garcs wrote: > Nope.. left the root_fs mounted on loop, and did a watch "df -i", and > this is what i see: > > /uml/root_fs 0 0 0 - /uml/loop Are you sure you're mounting the filesystem correctly? This is how I do it on my machine: joni:~# mkdir /mnt/tmp joni:~# mount -o loop /root/root_fs /mnt/tmp joni:~# df -i /mnt/tmp Filesystem Inodes IUsed IFree IUse% Mounted on /root/root_fs 15808 11124 4684 71% /mnt/tmp joni:~# So here you can see that 71% of the inodes are used up. You should also do a regular `df /mnt/tmp' to see how much of the filesystem is actually used. If these commands show that the filesystem still has space, you might want to have a look to see what that init script is doing - it looks like it's using tar to create device nodes but that's failing. Just using static device nodes rather than udev might be a simpler way to get it working. Have you tried any other guest filesystems? -- Ruaidhri |
From: <mar...@gm...> - 2005-08-11 17:52:55
|
---------- Forwarded message ---------- From: Ruaidhri Power <rua...@ne...> Date: Aug 11, 2005 3:20 PM Subject: Re: Fwd: [uml-user] booting To: use...@li... On Thu, Aug 11, 2005 at 03:02:44PM +0000, Marco Garcs wrote: > Nope.. left the root_fs mounted on loop, and did a watch "df -i", and > this is what i see: > > /uml/root_fs 0 0 0 - /uml/loop Are you sure you're mounting the filesystem correctly? This is how I do it on my machine: joni:~# mkdir /mnt/tmp joni:~# mount -o loop /root/root_fs /mnt/tmp joni:~# df -i /mnt/tmp Filesystem Inodes IUsed IFree IUse% Mounted on /root/root_fs 15808 11124 4684 71% /mnt/tmp joni:~# So here you can see that 71% of the inodes are used up. You should also do a regular `df /mnt/tmp' to see how much of the filesystem is actually used. If these commands show that the filesystem still has space, you might want to have a look to see what that init script is doing - it looks like it's using tar to create device nodes but that's failing. Just using static device nodes rather than udev might be a simpler way to get it working. Have you tried any other guest filesystems? -- Ruaidhri ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ User-mode-linux-user mailing list Use...@li... https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user How exactly do i use static device nodes instead of udev? sorry.. but im a newbie on this.... |
From: Ruaidhri P. <rua...@ne...> - 2005-08-11 21:23:13
|
On Thu, Aug 11, 2005 at 05:52:39PM +0000, Marco Garces wrote: > How exactly do i use static device nodes instead of udev? sorry.. but > im a newbie on this.... I'd suggest you do three things: First, try another guest image to make sure that works - particularly if it might fulfill your needs. There's no point spending time fixing this image if that's the case. If not, then loopback mount the filesystem and have a look at the script that's failing. Maybe try disabling it and see what happens. I think you need to understand more about what the error is before you can fix it. Finally, if you do need to disable udev, have a look at this page so you know how udev works on Gentoo: http://www.gentoo.org/doc/en/udev-guide.xml Then remove all the packages *from the guest* that page tells you to install, and run the following command to make the device nodes. chroot /path/to/mounted/guest /bin/sh -c 'cd /dev && ./MAKEDEV ubd' Make sure you aren't just creating these devices on the host, they're no use there. When you run the guest again, run it with devfs=nomount on the command line, just to make sure devfs doesn't start. -- Ruaidhri |
From: Jeff D. <jd...@ad...> - 2005-08-11 23:30:48
|
On Thu, Aug 11, 2005 at 12:45:20PM +0000, Marco Garc?s wrote: > No, the root_fs has enough space.... i know 4 sure! :( any more ideas? A sparse root_fs with no space left on the host filesystem? Jeff |
From: Blaisorblade <bla...@ya...> - 2005-08-12 13:44:54
|
On Wednesday 10 August 2005 19:32, Nelson Castillo wrote: > > [ oops ] > > > > * The "tar" command failed with error: > > > > rd/c6d27p4: Cannot mknod: No space left on device > > tar: rd/c6d27p5: Cannot mknod: No space left on device > > tar: rd/c6d27p6: Cannot mknod: No space left on device > > tar: rd/c6d27p7: Cannot mknod: No space left on device > > tar: rd/c6d28p1: Cannot mknod: No space left on device > > tar: rd/c6d28p2: Cannot mknod: No space left on device > > tar: rd/c6d28p3: Cannot mknod: No space left on device > > tar: rd/c6d28p4: Cannot mknod: No space left on device > > ... > > ...... > > so on so on...... > > > > What seems to be the problem? Any ideas? Thanks in advance... > > Is your root_fs full? > > Mount it with -o loop as root and run df to check. On my Gentoo /dev is a ramfs/tmpfs filesystem, so make sure you give the guest enough memory... -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: <mar...@gm...> - 2005-08-12 13:52:31
|
>On my Gentoo /dev is a ramfs/tmpfs filesystem, so make sure you give the g= uest >enough memory... I gave 2gb of swap to my guest!!! I'm now going in other direction. Instead of building from stage 3 and then, tar everything, decided to mount directly the root_fs on a loop, and go stage3 from their. Already noticed some differences, and this latest problem disappeared. Will post the problems later, for help, but now I'm not @ work. Thank 4 your help... Just one thing: isn't the uml site a bit... old? Not updated i guess... old root_fs! Well, maybe just my sensation... Marco Garc=EAs |