mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Dave Mielke <dave@mielke.cc>
Cc: "Linux Kernel (mailing list)" <linux-kernel@vger.kernel.org>
Subject: Re: nfs mount by label not working.
Date: Thu, 24 May 2001 00:13:35 +0200	[thread overview]
Message-ID: <20010524001335.A11589@win.tue.nl> (raw)
In-Reply-To: <20010523231213.A11564@win.tue.nl> <Pine.LNX.4.30.0105231728430.995-100000@dave.private.mielke.cc>
In-Reply-To: <Pine.LNX.4.30.0105231728430.995-100000@dave.private.mielke.cc>; from Dave Mielke on Wed, May 23, 2001 at 05:34:22PM -0400

On Wed, May 23, 2001 at 05:34:22PM -0400, Dave Mielke wrote:

> I presume that you're assuming that my /proc/partitions is empty because its
> size shows as 0:
>
>     ls -l /proc/partitions
>     -r--r--r--   1 root     root            0 May 23 17:31 /proc/partitions

Ah, yes, sorry - I was too quick here.

> It does, however, have several lines in it.
>
>     cat /proc/partitions
>     major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse running use aveq
>
>        3     0    6297480 hda      119 141 520 1790 0 0 0 0 0 1180 1790

But this is full of strange numbers that someone saw fit to add to /proc/partitions.
What a bad idea!

If someone changes /proc/partitions then probably the old utilities that used it
are broken. I do not have a memory, but it seems I recall fixing this already.
Try a recent mount, say from util-linux 2.11d.

[But you show IDE disks, but the subject line talks about NFS mounts?]

Andries

  reply	other threads:[~2001-05-23 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 19:11 Dave Mielke
2001-05-23 20:23 ` Tim Moore
2001-05-23 21:12 ` Guest section DW
2001-05-23 21:34   ` Dave Mielke
2001-05-23 22:13     ` Guest section DW [this message]
2001-05-24  7:31 ` Philipp Matthias Hahn
2001-05-24 23:52   ` Dave Mielke

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=20010524001335.A11589@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=dave@mielke.cc \
    --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

all inboxes | Powered by JetHome®