From: Eric Sandeen <sandeen@sandeen.net>
To: jamesb@loreland.org
Cc: xfs@oss.sgi.com
Subject: Re: New CentOS4/RHEL4-compatible xfs module rpms
Date: Thu, 19 Jul 2007 10:15:17 -0500 [thread overview]
Message-ID: <469F8005.3080104@sandeen.net> (raw)
In-Reply-To: <48478.193.203.83.22.1184855825.squirrel@colo.loreland.org>
James Braid wrote:
>> http://sandeen.net/rhel4_xfs/kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
>>
>
> Has anyone had any luck with getting NFS exports to work with these
> updated modules? I'm not having any luck, and just getting "Permission
> denied" errors when trying to mount an NFS exported filesystem using these
> modules. Works fine with the stock modules from a rebuilt RHEL4 kernel.
That's odd. You have the module on the server, exporting an xfs
filesystem, and you're getting permission denied on the client?
-Eric
next prev parent reply other threads:[~2007-07-19 15:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 19:07 New CentOS4/RHEL4-compatible xfs module rpms Eric Sandeen
2006-12-07 17:25 ` Geir A. Myrestrand
2006-12-07 17:52 ` Eric Sandeen
2006-12-07 18:17 ` Geir A. Myrestrand
2006-12-07 23:26 ` David Chinner
2006-12-08 2:58 ` Geir A. Myrestrand
2006-12-07 18:19 ` Geir A. Myrestrand
2006-12-07 20:51 ` Geir A. Myrestrand
2006-12-07 21:11 ` Nathan Scott
2006-12-07 21:35 ` Geir A. Myrestrand
2006-12-07 21:40 ` Nathan Scott
2006-12-07 21:51 ` Geir A. Myrestrand
2006-12-07 22:06 ` Nathan Scott
2006-12-07 22:16 ` Geir A. Myrestrand
2006-12-07 22:18 ` Eric Sandeen
2006-12-07 22:25 ` Geir A. Myrestrand
2006-12-07 22:30 ` Eric Sandeen
2006-12-07 22:52 ` Geir A. Myrestrand
2006-12-07 22:53 ` Eric Sandeen
2006-12-07 23:08 ` Geir A. Myrestrand
2007-07-19 14:37 ` James Braid
2007-07-19 15:15 ` Eric Sandeen [this message]
2007-07-21 3:34 ` James Braid
2007-07-21 14:58 ` Eric Sandeen
2007-07-21 15:36 ` James Braid
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:04 James Pearson
2007-08-08 16:09 ` Eric Sandeen
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=469F8005.3080104@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jamesb@loreland.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.