From: Steve Dickson <SteveD@redhat.com>
To: Venkatesh KS <venkatesh.ks@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] linux nfs mount command crashes
Date: Tue, 01 Apr 2008 18:32:39 -0400 [thread overview]
Message-ID: <47F2B807.3090703@RedHat.com> (raw)
In-Reply-To: <4cf2912c0804010950m1994b9eal78a9f2695945d554-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Venkatesh KS wrote:
> It turns out that the date on the client is set to 2144. But still libc
> should report and error and not crash.
I completely agree... Unfortunately we (the NFS community) has
no control over glibc RPC code at all... and the glibc people have
very little, if any, desire to fix this types of bugs...
So, unfortunately, it is what is is... :-(
steved.
>
> -venkatesh
>
> On Tue, Apr 1, 2008 at 8:38 PM, Venkatesh KS <venkatesh.ks@gmail.com
> <mailto:venkatesh.ks@gmail.com>> wrote:
>
> Hi,
>
> The linux nfs mount command crashes here
>
> Core was generated by `/sbin/mount.nfs
> 10.10.3.136:/localdisk/msgLog/msgLog1 /mnt -o rw'.
> Program terminated with signal 6, Aborted.
> #0 0x00002adc4dde6065 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00002adc4dde6065 in raise () from /lib64/libc.so.6
> #1 0x00002adc4dde7b00 in abort () from /lib64/libc.so.6
> #2 0x00002adc4dea5d7d in authunix_create_internal () from
> /lib64/libc.so.6
> #3 0x00002adc4dea586f in authunix_create_default_internal () from
> /lib64/libc.so.6
> #4 0x000055555555cbfc in ?? () from /sbin/mount.nfs
> #5 0x0000555555559d3a in ?? () from /sbin/mount.nfs
> #6 0x0000555555557f0a in main () from /sbin/mount.nfs
>
> I am not able to get any info about the libc functions. Have anyone
> see this before?
>
> The mount command from a different machine to the server succeeds.
> And this mount
> was working sometime back from the same machine as well.
>
> regards,
> -venkatesh
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> _______________________________________________
> Please note that nfs@lists.sourceforge.net is being discontinued.
> Please subscribe to linux-nfs@vger.kernel.org instead.
> http://vger.kernel.org/vger-lists.html#linux-nfs
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
parent reply other threads:[~2008-04-01 22:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4cf2912c0804010950m1994b9eal78a9f2695945d554-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
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=47F2B807.3090703@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=venkatesh.ks@gmail.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