From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 patch] NFS filehandle check
Date: Thu, 08 Feb 2007 09:12:35 +0000 [thread overview]
Message-ID: <1170925955.11001.444.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <1170886994.7725.2.camel@d-cthon07-w-63.Connectathon.ORG>
Hi,
On Wed, 2007-02-07 at 17:23 -0500, Wendy Cheng wrote:
> On Wed, 2007-02-07 at 10:31 +0000, Steven Whitehouse wrote:
> > Hi,
> >
> > Did you intend to leave that printk in there?
>
> Yes .. will that be an issue ?
>
I presume that it doesn't trigger in normal use? or at least the thing
I'm worried about is that we'll fill up peoples logs if this happens too
often.
> BTW, GFS2 can't support NFS V2 at this moment (since its max fh size is
> 32 bytes while GFS2 requires 40 bytes fh).
>
> -- Wendy
>
Ok, we might be able to make some changes there I think,
Steve.
next prev parent reply other threads:[~2007-02-08 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 23:52 [Cluster-devel] [GFS2 patch] NFS filehandle check Wendy Cheng
2007-02-07 10:31 ` Steven Whitehouse
2007-02-07 22:23 ` Wendy Cheng
2007-02-08 9:12 ` Steven Whitehouse [this message]
2007-02-23 5:21 ` Wendy Cheng
2007-02-23 11:46 ` Steven Whitehouse
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=1170925955.11001.444.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).