Well, looking at the Bugzilla, it looks like they are asking you to contact
your support rep. If you are working in the government, there will be a TAM
assigned to handle these problems. If you are a contractor working on
systems to be delivered to the government, then you need to be a paying
customer to expect support from Red Hat. Especially when your original
problem manifested on CentOS. Granted, it's the same code base, but that
doesn't make your problem on CentOS, a problem for Red Hat.
As far as when you get to be antagonistic goes, never if you want to be
professional about it....
Now, all that said and done, here are some questions for you which might
help us figure what would help.
1. What options are present on the mount? (cat /proc/mounts, thinks like
sync can be a problem)
2. What does your /etc/exports config look like on your server node (cat
/etc/exports)
3. You are using NFSv4, are you using Kerberos with it?
3.a. If so, what mode are you using for your gss/krb flag? (krb5,
krb5i, krb5p)
4. What's your network speed? Are you sure? (ethtool ethX to make sure)
5. Selinux?
6. Auditing?
7. How many clients are hitting your server and how many nfsd threads are
you running on it?
This is by no means an exhaustive list of things to look at.
Anyway, in order to get any real help, you cannot just shout out, "My stuff
is broke, it's Red Hat's fault, no one will listen to me!"
Give us something to work with.
By the way, in looking at the responses to your bugzilla, it doesn't look
to me like they were shamed into responding. It looks like are telling you
to go through proper channels if they exist. full stop.
Ideally, you'll get this resolved using your assigned TAM etc, however I am
sure others as well as I are happy to help if you are willing to be
professional about it.
Corey
RHCA #*110-541-489*
On Tue, Jul 10, 2012 at 9:48 AM, <m.roth@xxxxxxxxx> wrote:
> Corey Kovacs wrote:
> > Maybe it takes posting your config to the list so we can see if you made
> a
>
> The config's the same for 5.8 and 6.3, I think. I do know my manager
> worked on it some, and had done some work with NFS 4 configuration.
>
> I can check with my manager, but I believe that we'd be willing to send
> that to RHEL; I don't know that he'd want it posted publicly, for security
> reasons (but I could be wrong; I'll ask him).
>
> > mistake. Are you a paying customer actually using RHEL? If this a real
> bug
> > I doubt it would be so ignored. Anyone else having a similar problem?
>
> This is 100% reproducible. A user found it on CentOS 6.2; we tried it on
> several servers, then went to an RHEL one. All identical responses.
> >
> > Lets start by being sensible and not antagonistic.
>
> At what point would you decide to "allow" me to be antagonistic?
>
> Let me restate my case: I opened a bugzilla case under my own account.
> After weeks, I used the email address for support: yes, we *do* have a
> contract with RHEL, and we are a US federal gov't agency. It's been
> something like two weeks, and I've not seen a response.
>
> The *only* thing that happened on the bug was they waited about a month,
> then there was a followup, if you read it, that they were on 6.3, and so
> they put it to dontfix.
>
> *That's* why I'm posting all over. This is the *first* responses I've
> gotten. I guess it *does* take public humiliation.
>
> mark
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
