Re: /proc/partitions not done updating when init is ran?

From: Marcos D. Marado Torres
Date: Thu Feb 12 2004 - 00:00:11 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Is that happening in 2.6.2-rc3-mm1 or up?

If yes, try unsetting nbd in your kernel config.

Mind Booster Noori

- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@xxxxxxxxxxxxxxxxx
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================

On Wed, 11 Feb 2004, Nick Bartos wrote:

> I have a problem where it does not look like /proc/partitions is updated
> completely by the time init is ran.
>
> Basically I am booting from a usb flash device, and when I try to run fsck
> on the device on boot (using LABEL=, which is necessary since the actual
> device cannot be assumed in my config) it fails. After further
> investigation /proc/partitions does not contain any scsi partitions right
> when init is starting, but if I do a "sleep 10" before running fsck then
> it works fine.
>
> I can of course put that sleep in there but that is ugly and I have no way
> of knowing the maximum delay, so if it took too long then it would not
> work and I would be screwed...
>
> Isn't /proc/partitions supposted to be finished updating when init starts?
> If this is not a kernel bug (or it won't be fixed for a while), then what
> is the deal and how can I fix this cleanly?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFAKwf2mNlq8m+oD34RAvICAJ94Kv1Yspu0syE8MLAZwSHEgJ8i4ACdEOJy
KqWcNxWT9t3o1jm1gUq04Ew=
=u2Ds
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/