From: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
To: Nick Bartos <spam99@2thebatcave.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/partitions not done updating when init is ran?
Date: Thu, 12 Feb 2004 04:58:27 +0000 (WET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402120457250.28596@student.dei.uc.pt> (raw)
In-Reply-To: <46246.192.168.1.12.1076553774.squirrel@mail.2thebatcave.com>
-----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@student.dei.uc.pt
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@vger.kernel.org
> 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-----
next prev parent reply other threads:[~2004-02-12 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 2:42 Nick Bartos
2004-02-12 4:58 ` Marcos D. Marado Torres [this message]
2004-02-12 12:47 ` Nick Bartos
2004-02-12 13:00 ` Nick Bartos
2004-02-12 17:16 ` Marcos D. Marado Torres
2004-02-13 0:40 ` Nick Bartos
2004-02-13 3:28 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0402120457250.28596@student.dei.uc.pt \
--to=marado@student.dei.uc.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=spam99@2thebatcave.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®