Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*mkinitrd\s+hang\s*$/: 12 ]

Total 12 documents matching your query.

1. mkinitrd hang (score: 1)
Author: "William L. Jones" <jones@xxxxxxxxxxxxxx>
Date: Thu, 03 May 2001 22:26:53 -0500
mkinitrd is hanging on a mkfs on the loop back device. Has any one seen this problem. I am runing linux-2.4-xfs-r1.0 build with kcc on a amd running Redhat 7.1. Bil Jones
/archives/xfs/2001-05/msg00242.html (8,721 bytes)

2. Re: mkinitrd hang (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Thu, 03 May 2001 22:39:06 -0500
Was this installed from our RPMs, or did you patch a vanilla kernel yourself, or do a cvs checkout? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc.
/archives/xfs/2001-05/msg00243.html (8,753 bytes)

3. Re: mkinitrd hang (score: 1)
Author: Walt H <waltabbyh@xxxxxxxxxx>
Date: Thu, 03 May 2001 20:52:23 -0700
Oops. Looks like you got bit by the infamout loop fs bug. It didn't get fixed until 2.4.3. If you can, boot into a different kernel version and run mkinitrd. Also, if I recall correctly, there was a
/archives/xfs/2001-05/msg00244.html (7,166 bytes)

4. Re: mkinitrd hang (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Thu, 03 May 2001 22:48:31 -0500
Sorry, I should complete that thought. :) If you patched your own kernel, and especially if you did a cvs checkout, the loop device is probably broken (it was broken in Linus' tree at least through 2
/archives/xfs/2001-05/msg00245.html (9,459 bytes)

5. Re: mkinitrd hang (score: 1)
Author: "William L. Jones" <jones@xxxxxxxxxxxxxx>
Date: Fri, 04 May 2001 09:20:46 -0500
Was this installed from our RPMs, or did you patch a vanilla kernel yourself, or do a cvs checkout? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc.
/archives/xfs/2001-05/msg00263.html (9,176 bytes)

6. Re: mkinitrd hang (score: 1)
Author: "William L. Jones" <jones@xxxxxxxxxxxxxx>
Date: Fri, 04 May 2001 09:27:36 -0500
Redhat 7.1. Sorry, I should complete that thought. :) If you patched your own kernel, and especially if you did a cvs checkout, the loop device is probably broken (it was broken in Linus' tree at lea
/archives/xfs/2001-05/msg00265.html (10,299 bytes)

7. mkinitrd hang (score: 1)
Author: xxxxxxxxxxx>
Date: Thu, 03 May 2001 22:26:53 -0500
mkinitrd is hanging on a mkfs on the loop back device. Has any one seen this problem. I am runing linux-2.4-xfs-r1.0 build with kcc on a amd running Redhat 7.1. Bil Jones
/archives/xfs/2001-05/msg01606.html (8,721 bytes)

8. Re: mkinitrd hang (score: 1)
Author: xxxxxxxxxxx>
Date: Thu, 03 May 2001 22:39:06 -0500
Was this installed from our RPMs, or did you patch a vanilla kernel yourself, or do a cvs checkout? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc.
/archives/xfs/2001-05/msg01607.html (8,753 bytes)

9. Re: mkinitrd hang (score: 1)
Author: een@xxxxxxx>
Date: Thu, 03 May 2001 20:52:23 -0700
Oops. Looks like you got bit by the infamout loop fs bug. It didn't get fixed until 2.4.3. If you can, boot into a different kernel version and run mkinitrd. Also, if I recall correctly, there was a
/archives/xfs/2001-05/msg01608.html (7,166 bytes)

10. Re: mkinitrd hang (score: 1)
Author: @xxxxxxxxxx>
Date: Thu, 03 May 2001 22:48:31 -0500
Sorry, I should complete that thought. :) If you patched your own kernel, and especially if you did a cvs checkout, the loop device is probably broken (it was broken in Linus' tree at least through 2
/archives/xfs/2001-05/msg01609.html (9,459 bytes)

11. Re: mkinitrd hang (score: 1)
Author: xxxxxxxxxxx>
Date: Fri, 04 May 2001 09:20:46 -0500
Was this installed from our RPMs, or did you patch a vanilla kernel yourself, or do a cvs checkout? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc.
/archives/xfs/2001-05/msg01627.html (9,176 bytes)

12. Re: mkinitrd hang (score: 1)
Author: xxxxxxxxxxx>
Date: Fri, 04 May 2001 09:27:36 -0500
Redhat 7.1. Sorry, I should complete that thought. :) If you patched your own kernel, and especially if you did a cvs checkout, the loop device is probably broken (it was broken in Linus' tree at lea
/archives/xfs/2001-05/msg01629.html (10,299 bytes)


This search system is powered by Namazu