From: Oleg Drokin <green@namesys.com>
To: Nils O. =?ISO-8859-1?Q?Sel=E5sdal ?= <noselasd@Utel.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS & NFS oops
Date: Thu, 20 Jun 2002 12:42:46 +0400 [thread overview]
Message-ID: <20020620124246.A1020@namesys.com> (raw)
In-Reply-To: <200206181041.g5IAfpL20399@localhost.localdomain>
Hello!
Can you reproduce this?
Bye,
Oleg
On Tue, Jun 18, 2002 at 12:41:51PM +0200, Nils O. =?ISO-8859-1?Q?Sel=E5sdal ?= wrote:
> Just wanted to know if this is a known problem and if it might be fixed in
> the near future:
> Using 2.4.19-pre8 just one filesystem with reiserfs, I exported a directory. Mounted
> it on another hosts and started writing a large (500mb) file to it, that resulted
> in the server filesystem going full and the server locked up hard.
>
> -
> NOS@Utel.no
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2002-06-20 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 10:41 ReiserFS & NFS oops Nils O. Selåsdal
2002-06-20 8:42 ` 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=20020620124246.A1020@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noselasd@Utel.no \
/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