The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Nils O. Selåsdal" <noselasd@frisurf.no>
To: linux-kernel@vger.kernel.org
Subject: df on a nfs mounted share vs local?
Date: 04 Jul 2002 16:35:04 +0200	[thread overview]
Message-ID: <1025793209.10267.5.camel@space> (raw)

Just wondering, how come df reports
root:~# df /mnt/export/
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda5              2562252    383792   2178460  15% /mnt/export
on the server, while on a client that mounts /mnt/export over nfs:
[root@space download]# df /mnt/nfs/
Filesystem           1k-blocks      Used Available Use% Mounted on
lfs:/mnt/export        2562256    383792   2178464  15% /mnt/nfs

Just a few blocks diffrent, but I've seen much bigger.. also seen +/-
a few % on "Use"

-- 
Nils Olav Selåsdal <NOS@Utel.no>
System Developer, UtelSystems a/s
w w w . u t e l s y s t e m s . c o m



             reply	other threads:[~2002-07-04 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 14:35 Nils O. Selåsdal [this message]
2002-07-05 12:35 ` df on a nfs mounted share vs local? Trond Myklebust

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=1025793209.10267.5.camel@space \
    --to=noselasd@frisurf.no \
    --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