From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bob Smart <smart@hpc.CSIRO.AU>
Cc: Pete Wyckoff <pw@osc.edu>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Red Hat needs this patch (was Re: handling NFSERR_JUKEBOX)
Date: 06 Nov 2001 10:05:19 +0100 [thread overview]
Message-ID: <shswv14w9ps.fsf@charged.uio.no> (raw)
In-Reply-To: <200111060521.QAA07024@trout.hpc.CSIRO.AU>
In-Reply-To: <200111060521.QAA07024@trout.hpc.CSIRO.AU>
>>>>> " " == Bob Smart <smart@hpc.CSIRO.AU> writes:
>> Take a look at the nfs sourceforge mailing list. There's a
>> long thread about this in the context of a Solaris HSM server.
>> I wrote a patch to try to do the right thing on a linux client,
>> but it is not perfect for many reasons:
>> http://devrandom.net/lists/archives/2001/6/NFS/0135.html
> Thanks again for this patch. I've appended our current version
> to save others the trouble of minor modifications. I've just
> tested it against 2.4.13-ac7.
> Your patch may not be perfect but it is a million times better
> than nothing. We have had no problems with it. Linux has a long
> tradition of utilizing imperfect software till something better
> comes along.
> This patch is ESSENTIAL to make Linux useable in large
> enterprises, because they increasingly commonly utilize
> hirearchically managed storage. I strongly urge
> Alan/Linus/Macello to include this patch in the stable kernel
> tree (but marked experimental). Or at least can the kernel
> maintainers at Red Hat and other distributions put it in their
> offerings: surely you see that you need this for your big
> customers.
The patch may appear to work, but it fails to understand the nature of
the problem. The problem with NFSERR_JUKEBOX is that is can appear in
more or less *any* NFSv3 RPC call. That includes everything from
lookups to writes.
If all you do is intercept read and setattr, then you certainly
haven't achieved 'enterprise quality'.
Cheers,
Trond
next prev parent reply other threads:[~2001-11-06 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 0:23 handling NFSERR_JUKEBOX Bob Smart
2001-07-13 14:06 ` Pete Wyckoff
2001-11-06 5:21 ` Red Hat needs this patch (was Re: handling NFSERR_JUKEBOX) Bob Smart
2001-11-06 9:05 ` Trond Myklebust [this message]
2001-11-06 9:10 ` Marcelo Tosatti
2001-11-06 10:53 ` Trond Myklebust
2001-11-06 10:36 ` Bob Smart
2001-11-06 13:54 ` Trond Myklebust
2001-11-06 23:41 ` handling NFSERR_JUKEBOX Trond Myklebust
2001-11-08 16:20 ` Pete Wyckoff
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=shswv14w9ps.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pw@osc.edu \
--cc=smart@hpc.CSIRO.AU \
/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