On 7 Nov 2000, Chmouel Boudjnah wrote:
> "Gregory S. Youngblood" <[EMAIL PROTECTED]> writes:
>
> > The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16,
> > and 2.2.17. These are the secure kernels that Mandrake provides.
>
> can you try with a 2.2.17 kernel rpm standard (no
"Gregory S. Youngblood" <[EMAIL PROTECTED]> writes:
> The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16,
> and 2.2.17. These are the secure kernels that Mandrake provides.
can you try with a 2.2.17 kernel rpm standard (no smp no secure) ?
--
MandrakeSoft Inc
et up as a
gateway which is using rp-pppoe and acting as a gateway/firewall for a
windows and linux machine in a small network. As well as using ipmasqadm
for port forwarding.
The system works flawlessly, for about 24 to 72 hours. Then I start
getting:
grow_inodes: inode-max limit reached
repea
Hello all,
as to the problem I described earlier about mysterios growing of the used
inodes number - another strange thing happened. Without applying any
patch or any changes in the system, the /proc/sys/fs/inode-max was set to
132000. System continued to increase the number in the
/proc/sys/fs
On Fri, Sep 01, 2000 at 11:40:31AM +0200, Trond Myklebust wrote:
[...]
> > nlm_release_file() *does* grab the semaphore. That's the
> > problem.
>
> Which is why I'm proposing a solution: to split it into 2 functions.
>1st function does the semaphore manipulations and calls
>2n
> " " == Michael Riepe <[EMAIL PROTECTED]> writes:
>> Ugh. In that case, my personal preference would be to make
>> nlm_release_file() grab the semaphore, then call another
>> routine to do f_count-- and possible file cleanup which could
>> also be called by nlmsvc_traverse_sh
On Fri, Sep 01, 2000 at 12:37:21AM +0200, Trond Myklebust wrote:
> > " " == Michael Riepe <[EMAIL PROTECTED]> writes:
>
> > On Thu, Aug 31, 2000 at 03:23:43PM +0200, Trond Myklebust
> > wrote:
> >> Your patch does not seem correct to me. IMO you should rather
> >> be calling
> " " == Michael Riepe <[EMAIL PROTECTED]> writes:
> On Thu, Aug 31, 2000 at 03:23:43PM +0200, Trond Myklebust
> wrote:
>> Your patch does not seem correct to me. IMO you should rather
>> be calling nlm_release_file() in both cases where you applied
>> 'put_file()'.
On Thu, Aug 31, 2000 at 03:23:43PM +0200, Trond Myklebust wrote:
> Your patch does not seem correct to me. IMO you should rather be
> calling nlm_release_file() in both cases where you applied
> 'put_file()'.
No. In the first of two cases, lockd will call nlm_release_file()
on its own when th
> " " == Michael Riepe <[EMAIL PROTECTED]> writes:
> There is an inode leak in lockd, caused by a reference counting
> bug. It will appear when you use DOS/Windows clients to access
> a knfsd+lockd based NFS server, and it will crash the server
> sooner or later (a DOS at
Hello everybody,
On Wed, Aug 30, 2000 at 04:00:19PM +0300, Leonid Mamtchenkov wrote:
> Hello,
>
> In the archives of the lkml I have found a message from Peter Gervai
> ([EMAIL PROTECTED]) dated Tue Apr 25 2000 available here:
> http://boudicca.tux.org/hypermail/linux-kernel/2000week18/0317.ht
Hello,
In the archives of the lkml I have found a message from Peter Gervai
([EMAIL PROTECTED]) dated Tue Apr 25 2000 available here:
http://boudicca.tux.org/hypermail/linux-kernel/2000week18/0317.html
Unfortunately, I was not able to find any reply to that message.
Currently, one of our
12 matches
Mail list logo
