From: Andries Brouwer <aebr@win.tue.nl>
To: jiri.wichern@hccnet.nl
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: PROBLEM: kernel 2.4.20 option CONFIG_BLK_STATS breaks /proc/partitons so "mount" can't mount devices by UUID.
Date: Tue, 17 Dec 2002 01:55:39 +0100 [thread overview]
Message-ID: <20021217005539.GA11900@win.tue.nl> (raw)
In-Reply-To: <3DFE6ED2.7174.1395ABF@localhost>
On Tue, Dec 17, 2002 at 12:24:50AM +0100, jiri.wichern@hccnet.nl wrote:
> Short description of the problem: You can't mount hard drive
> volumes by using their UUID number when also using extra
> statistics for your block devices by the CONFIG_BLK_STATS
> kernel option.
Yes, we know.
You use an old version of mount, and the mount will always fail.
Two solutions:
(i) Do not use CONFIG_BLK_STATS.
(ii) Upgrade mount to a recent version (mount is part of util-linux,
recent is for example 2.11y).
Note that solution (ii) gives you a situation where mount and fdisk
fail sporadically instead of always, maybe not precisely what one
had hoped. Thus, (i) is the preferred solution.
It was really bad that CONFIG_BLK_STATS went into 2.4.20,
but you need not use it.
Andries
Two months ago I sent the below Doc patch. It is still needed.
--- Documentation/Configure.help~ Mon Oct 14 01:12:13 2002
+++ Documentation/Configure.help Tue Oct 22 20:30:39 2002
@@ -561,6 +561,8 @@
This is required for the full functionality of sar(8) and interesting
if you want to do performance tuning, by tweaking the elevator, e.g.
+ On the other hand, it will cause random and mysterious failures for
+ fdisk, mount and other programs reading /proc/partitions.
If unsure, say N.
(this is about CONFIG_BLK_STATS).
next prev parent reply other threads:[~2002-12-17 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 23:24 PROBLEM: kernel 2.4.20 option CONFIG_BLK_STATS breaks /proc/partitons so "mount" can't mount devices by UUID jiri.wichern
2002-12-17 0:55 ` Andries Brouwer [this message]
2002-12-18 15:31 ` Marcelo Tosatti
2002-12-19 11:51 ` Andries Brouwer
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=20021217005539.GA11900@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=jiri.wichern@hccnet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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