From: Venkata Ravella <Venkata.Ravella@synopsys.com>
To: raven@themaw.net
Cc: linux-kernel@vger.kernel.org, Ramki.Balasubramanium@synopsys.COM,
ab@californiadigital.com, hpa@zytor.com, autofs@linux.kernel.org
Subject: Re: Automount/NFS issues causing executables to appear corrupted
Date: Mon, 19 Apr 2004 17:08:35 -0700 (PDT) [thread overview]
Message-ID: <200404200008.i3K08Zvs018948@radium.internal.synopsys.com> (raw)
autofs version is autofs-3.1.7-21
I also have one new update. We started seeing similar problem on
the system running the kernel 2.4.18-e.12smp which has the same
version(3.1.7-21) of autofs as well.
This may or may not be an autofs problem but, restarting autofs
fixes this problem temporarily.
>
>Please cc autofs questions to the list at autofs@linux.kernel.org.
>
>On Sun, 18 Apr 2004, Venkata Ravella wrote:
>
>>
>> The current kernel we use is default 7.2 kernel with two modifications:
>> 1) BM patch applied to extend address space for a single process to 3.6GB
>> 2) mnt patch applied to allow upto 1024 nfs mount points
>>
>> uname -r output:
>> 2.4.7-10mntBMsmp
>
>What autofs version?
>
>To be honest it's a bit hard to see how this is an autofs issue.
>Mind, having said that, ....
>
>Ian
next reply other threads:[~2004-04-20 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 0:08 Venkata Ravella [this message]
2004-04-20 0:24 ` Automount/NFS issues causing executables to appear corrupted H. Peter Anvin
2004-04-20 1:27 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2004-04-18 21:23 Venkata Ravella
2004-04-18 23:06 ` H. Peter Anvin
2004-04-19 1:07 ` Ian Kent
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=200404200008.i3K08Zvs018948@radium.internal.synopsys.com \
--to=venkata.ravella@synopsys.com \
--cc=Ramki.Balasubramanium@synopsys.COM \
--cc=ab@californiadigital.com \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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