From: Andries Brouwer <aebr@win.tue.nl>
To: Alastair Stevens <alastair@camlinux.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Small oddity of the week: 2.4.20-pre
Date: Sat, 12 Oct 2002 20:00:32 +0200 [thread overview]
Message-ID: <20021012180032.GA22980@win.tue.nl> (raw)
In-Reply-To: <1034443816.10850.70.camel@dolphin.entropy.net>
On Sat, Oct 12, 2002 at 06:30:15PM +0100, Alastair Stevens wrote:
> > > fdisk -l | grep -w "/dev/hda6"
> > >
> > > For some reason, this now produces, entirely at _random_, either one or
> > > two lines of output! It was the duplicated output that broke Mindi.
>
> Here's a typical output:
>
> 1 root@dolphin:/home/alastair> fdisk -l | grep -w "/dev/hda6"
> /dev/hda6 4419 4749 2658726 83 Linux
> /dev/hda6 4419 4749 2658726 83 Linux
> 2 root@dolphin:/home/alastair> fdisk -l | grep -w "/dev/hda6"
> /dev/hda6 4419 4749 2658726 83 Linux
> 3 root@dolphin:/home/alastair> fdisk -l | grep -w "/dev/hda6"
> /dev/hda6 4419 4749 2658726 83 Linux
> 4 root@dolphin:/home/alastair> fdisk -l | grep -w "/dev/hda6"
> /dev/hda6 4419 4749 2658726 83 Linux
>
> ie - the first time, it gives me two repeated lines. This appears to be
> random. In a clean terminal, it'll sometimes give me only the one line
> on the first run, and then do two lines multiple times....
Could it be that you have statistics garbage in /proc/partitions?
That will break fdisk.
next prev parent reply other threads:[~2002-10-12 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 14:00 Small oddity of the week: 2.4.20-pre Alastair Stevens
[not found] ` <20021012171642.GA22969@win.tue.nl>
[not found] ` <1034443816.10850.70.camel@dolphin.entropy.net>
2002-10-12 18:00 ` Andries Brouwer [this message]
[not found] ` <1034447457.2688.74.camel@dolphin.entropy.net>
2002-10-12 22:46 ` Andries Brouwer
2002-10-22 10:20 ` Alan Cox
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=20021012180032.GA22980@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=alastair@camlinux.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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