Re: [ILUG] mkinitrd and non-RH kernels

From: Philip Reynolds (phil at domain redbrick.dcu.ie)
Date: Thu 05 Sep 2002 - 08:51:36 IST

Next message: John P. Looney: "[ILUG] file handle debugging"
Previous message: bulawa mulete jr: "[ILUG] assistance needed"
In reply to: Paul Jakma: "Re: [ILUG] mkinitrd and non-RH kernels"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

Paul Jakma's [paulj at domain alphyra.ie] 77 lines of wisdom included:
> # dd if=/dev/zero of=/tmp/initrd.img.tIUezw bs=1k
> count=3000
> 3000+0 records in
> 3000+0 records out
> # losetup /dev/loop0
> loop: can't get info on device /dev/loop0: No such device or address
> (as expected - device isnt setup)
> # losetup /dev/loop0 /tmp/initrd.img.tIUezw
> ioctl: LOOP_SET_FD: Invalid argument
> # strace losetup /dev/loop0 /tmp/initrd.img.tIUezw
> [snippage]
> open("/tmp/initrd.img.tIUezw", O_RDWR|O_LARGEFILE) = 3
> open("/dev/loop0", O_RDWR|O_LARGEFILE) = 4
> mlockall(MCL_CURRENT|MCL_FUTURE) = 0
> ioctl(4, 0x4c00, 0x3) = -1 EINVAL (Invalid argument)

If ioctl is failing then your loop device isn't working. This means
whatever created that loopback device isn't doing it's job properly.

Phil.

-- 
  Philip Reynolds        
   RFC Networks          tel: 01 8832063
www.rfc-networks.ie      fax: 01 8832041

Next message: John P. Looney: "[ILUG] file handle debugging"
Previous message: bulawa mulete jr: "[ILUG] assistance needed"
In reply to: Paul Jakma: "Re: [ILUG] mkinitrd and non-RH kernels"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:18:40 GMT