[DragonFlyBSD - Bug #2297] strange NFS (client) error messages / problems

[Stefan Krüger via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2297 has been updated by Stefan Krüger.


Another thing:

cosmicdj@dfly:/home/cosmicdj/tmp/dflybsd > ./dfly-fsx test.fsx.dat
truncating to largest ever: 0x13e76
LOG DUMP (4 total operations):
1(1 mod 256): TRUNCATE UP       from 0x0 to 0x13e76LOG DUMP (4 total operations):
^C1(1 mod 256): TRUNCATE UP     from 0x0 to 0x13e76signal 2
testcalls = 4

vs.

cosmicdj@dfly:/home/cosmicdj/tmp/dflybsd > ./dfly-fsx -W -R test.fsx.dat
mapped writes DISABLED
truncating to largest ever: 0x32740
truncating to largest ever: 0x39212
truncating to largest ever: 0x3bae9
truncating to largest ever: 0x3c1e3
truncating to largest ever: 0x3d1cd
truncating to largest ever: 0x3e8b8
truncating to largest ever: 0x3ed14
truncating to largest ever: 0x3f9c2
truncating to largest ever: 0x3ff9f
truncating to largest ever: 0x3ffa9
^Csignal 2
testcalls = 8973

----------------------------------------
Bug #2297: strange NFS (client) error messages / problems
http://bugs.dragonflybsd.org/issues/2297

Author: Stefan Krüger
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 


Hi,

I have DragonFly mounting my home dir via NFS (server is running Fedora 16) and noticed the following warnings on the console:

dfly.my.lan kernel log messages:
> nfs send error 32 for server f16srv:/home/cosmicdj
> receive error 54 from nfs server f16srv:/home/cosmicdj
> nfs send error 32 for server f16srv:/home/cosmicdj
> receive error 54 from nfs server f16srv:/home/cosmicdj

+ tons more, always error 32 or 54

Today, I got this:

cosmicdj@dfly:/home/cosmicdj> ls
^T
load: 0.00  cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k
^C
^T
load: 0.00  cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k
^C
^Z
^T
load: 0.00  cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k

Connection to dflyclosed. (<- killed my shell)

I tried to kill 'ls', even via -9. Didn't help. So I ended up killing the shell and tried to umount/remount my NFS homedir via console:


root@dfly # umount /home/cosmicdj
^T
load: 0.00  cmd: umount 3295 [clock] 0.00u 0.00s 0% 1444k
[diagnostic] cache_lock: blocked on 0xffffffe07d31e7f8 ".history_beastie"
^C
^Z
^T
load: 0.00  cmd: umount 3295 [clock] 0.00u 0.09s 0% 1444k
[diagnostic] cache_lock: blocked on 0xffffffe07d319158 ""
[diagnostic] cache_lock: blocked on 0xffffffe07d319158 ""
[diagnostic] cache_lock: blocked on 0xffffffe07d319158 ""


I get "[diagnostic] cache_lock: blocked on 0xffffffe07d319158 """ errors when I try to login via ssh again (I guess sshd tries to read my key...)

So it was working fine, but after, say 1 day uptime it doesn't work anymore :(


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account