From: Oleg Drokin <green@namesys.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kswapd oops in 2.4.20 SMP+NFS
Date: Fri, 21 Mar 2003 16:56:28 +0300 [thread overview]
Message-ID: <20030321165628.K17440@namesys.com> (raw)
In-Reply-To: <1048245614.9338.41.camel@fortknox>
Hello!
On Fri, Mar 21, 2003 at 12:20:14PM +0100, Soeren Sonnenburg wrote:
> I just checked the logs... It seems that the oops occurs 24 seconds
> after the backup script was started (which is run hourly).
> This script first mounts the nfs share, then looks for modified files
> and tar's them over, then umounts the share.
> So it is probably the umount of that nfs partion.
Well, then I think NFS people may be interested in that oops.
Resend it to them please and state that this is most likely from NFS.
Thank you.
Bye,
Oleg
prev parent reply other threads:[~2003-03-21 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 14:23 kswapd oops in 2.4.20 SMP+NFS Soeren Sonnenburg
2003-03-21 8:28 ` Oleg Drokin
2003-03-21 8:36 ` Soeren Sonnenburg
2003-03-21 9:50 ` Soeren Sonnenburg
2003-03-21 10:04 ` Oleg Drokin
[not found] ` <1048243299.9338.23.camel@fortknox>
[not found] ` <20030321135841.D17440@namesys.com>
2003-03-21 11:20 ` Soeren Sonnenburg
2003-03-21 13:56 ` Oleg Drokin [this message]
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=20030321165628.K17440@namesys.com \
--to=green@namesys.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
/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