From: Soeren Sonnenburg <reiserfs@nn7.de>
To: Oleg Drokin <green@namesys.com>
Cc: Bernd Schubert <bernd-schubert@web.de>,
'reiserfs' <reiserfs-list@namesys.com>
Subject: Re: no further nfsd-fh: found a name that I didn't expect
Date: 24 May 2003 09:18:32 +0200 [thread overview]
Message-ID: <1053760712.1213.18.camel@localhost> (raw)
In-Reply-To: <20030524070500.GA10706@namesys.com>
On Sat, 2003-05-24 at 09:05, Oleg Drokin wrote:
> Hello!
>
> On Fri, May 23, 2003 at 08:20:36PM +0200, Bernd Schubert wrote:
> > > > ever again. Well, we once rebooted and used by accident the wrong
> > > > kernel-image and of course had problems again until the next reboot.
> > > > Btw, is the iget4()-fix in 2.4.21-rc3 the same patch ?
> > > No, this is not iget5_locked (we plan to push it in 2.4.22pre time),
> > > this is minimal fix instead.
> > Great, so we won't see this problem even without patching.
>
> It seems so.
well it strongly seems so... as we also had this problem and it did also
not occur for the last 52 days since we applied that patch...
S.
prev parent reply other threads:[~2003-05-24 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 15:03 no further nfsd-fh: found a name that I didn't expect Bernd Schubert
2003-05-23 15:18 ` Oleg Drokin
2003-05-23 18:20 ` Bernd Schubert
2003-05-24 7:05 ` Oleg Drokin
2003-05-24 7:18 ` Soeren Sonnenburg [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=1053760712.1213.18.camel@localhost \
--to=reiserfs@nn7.de \
--cc=bernd-schubert@web.de \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.