From: Samuel Maftoul <maftoul@esrf.fr>
To: Hank Leininger <hlein@progressive-comp.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: /usr/bin/df reports false size on big NFS shares
Date: Mon, 10 Jun 2002 21:03:58 +0200 [thread overview]
Message-ID: <20020610210358.A16994@pcmaftoul.esrf.fr> (raw)
In-Reply-To: <200206101839.g5AIdDo29997@marc2.theaimsgroup.com>
On Mon, Jun 10, 2002 at 02:39:13PM -0400, Hank Leininger wrote:
> Most distributions ship slightly (or heavily) patched kernels. Above you
> can see the 2.4.4 kernel is not stock, it is named '2.4.4-4GB' for one
> thing, which most likely means it is tweaked for a 4GB memory system? That
> may be how SuSE shipped kernels for 7.2, idunno. But the point is, it is
> likely that stock 2.4.4 would not work either, it would have the same
> problem as 2.4.18. There's some added bits in SuSE's release kernel that
> make >1TB NFS shares happy. I'd suggest that you try booting 2.4.4 stock
I'm using 2.4.18 unofficial srpm from suse ftp server, we need this
because we have hudge needs ( scientific research institute).
I think mostly the same patche are applied.
I'll try to find a "pirate" RH system (we don't support it) at work and
see if the same behavious applies.
> just to see if it misbehaves the same way 2.4.18 does, and if so, start
> trying to figure out what SuSE patch fixes this for you (check SuSE
> specific lists, and/or ask their support). With luck you will find that
> either SuSE has a newer 2.4.x kernel with firewire support, or whatever
That's the point, their unofficial rpm's has it.
> they've done that fixes NFS can be extracted out and added to a current
> stock 2.4.x kernel source.
That probably won't be the case. :)
> --
> Hank Leininger <hlein@progressive-comp.com>
Sam
next prev parent reply other threads:[~2002-06-10 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 18:39 Hank Leininger
2002-06-10 19:03 ` Samuel Maftoul [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-10 14:54 Samuel Maftoul
2002-06-10 17:55 ` Andreas Dilger
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=20020610210358.A16994@pcmaftoul.esrf.fr \
--to=maftoul@esrf.fr \
--cc=hlein@progressive-comp.com \
--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®