All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 and NFS
Date: Wed, 08 Sep 2004 14:00:06 +0200	[thread overview]
Message-ID: <413EF446.1070001@fh-landshut.de> (raw)
In-Reply-To: <1094543842.1340.61.camel@tribesman.namesys.com>

Famous last log entries: ;)

On the target (NFSv3 client):

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.1.1
Looking up port of RPC 100005/1 on 192.168.1.1
VFS: Mounted root (nfs filesystem).
nfs_stat_to_errno: bad nfs status return value: 45
mount_devfs_fs(): unable to mount devfs, err: -5
Freeing unused kernel memory: 236k init
nfs_stat_to_errno: bad nfs status return value: 45
Warning: unable to open an initial console.
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
Rebooting in 180 seconds..

On the host (NFSv3 server):

Sep  8 13:50:31 ppcproject1 rpc.mountd: authenticated mount request from 
192.168.1.4:800 for /opt/devel/powerpc/rootfs (/opt/devel/powerpc/rootfs)
Sep  8 13:50:32 ppcproject1 kernel: reiser4_encode_fh-3: need=36, lenp=5
Sep  8 13:50:32 ppcproject1 last message repeated 5 times

Guess we've tripped a wire here! It triggered one of your printks...

With kind regards,
Oliver Korpilla

      parent reply	other threads:[~2004-09-08 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 12:53 Reiser4 and NFS Oliver Korpilla
2004-09-07  7:57 ` Vladimir Saveliev
2004-09-07  8:05   ` Oliver Korpilla
2004-09-07 14:00     ` Vladimir Saveliev
2004-09-07 14:18       ` Oliver Korpilla
2004-09-08 12:00   ` Oliver Korpilla [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=413EF446.1070001@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.