Re: [Moosefs-users] dbench on moosefs on freebsd

[Michal B. <mic...@ge...>]

Hi Andrey!

Unfortunately we couldn't recreate this error. Is this repeatable in your
environment? Can you give us some more tips how to recreate it? 


Kind regards
Michał Borychowski 
MooseFS Support Manager
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Gemius S.A.
ul. Wołoska 7, 02-672 Warszawa
Budynek MARS, klatka D
Tel.: +4822 874-41-00
Fax : +4822 874-41-01



-----Original Message-----
From: Andrey Belashkov [mailto:ma...@ca...] 
Sent: Tuesday, April 26, 2011 10:50 PM
To: moo...@li...
Subject: [Moosefs-users] dbench on moosefs on freebsd

Hello

We use moosefs 1.6.20 from ports on FreeBSD 8.2-RELEASE amd64 on ufs.

When we trying 'dbench 500' on moosefs share, after some time got in dmesg:
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
pid 3519 (mfsmount), uid 0: exited on signal 6 (core dumped)

and in shell with dbench:

 500       762    18.22 MB/sec  execute 373 sec  latency 12651.732 ms
 500       763    18.17 MB/sec  execute 374 sec  latency 13687.228 ms
 500       764    18.12 MB/sec  execute 375 sec  latency 14727.718 ms
[765] open ./clients/client309/~dmtmp/PWRPNT/NEWPCB.PPT failed for
handle 10032 (Device not configu
red)
[768] write failed on handle 10032 (Socket is not connected)
(766) ERROR: handle 10032 was not found
[768] write failed on handle 10032 (Device not configured)
[738] open ./clients/client272/~dmtmp/PWRPNT/NEWPCB.PPT failed for
handle 10026 (Socket is not connected)
(739) ERROR: handle 10026 was not found
[773] unlink ./clients/client204/~dmtmp/PWRPNT/PPTC112.TMP failed
(Socket is not connected) - expected NT_STATUS_OK
ERROR: child 204 failed at line 773
[768] write failed on handle 10032 (Socket is not connected)
Child failed with status 1
[718] open ./clients/client399/~dmtmp/PWRPNT/NEWPCB.PPT failed for
handle 10024 (Socket is not connected)
[710] rename ./clients/client136/~dmtmp/PWRPNT/NEWPCB.PPT
./clients/client136/~dmtmp/PWRPNT/PPTB1E4.TMP failed (Socket is not
connected) - expected NT_STATUS_OK
ERROR: child 136 failed at line 710
(719) ERROR: handle 10024 was not found
[710] rename ./clients/client455/~dmtmp/PWRPNT/NEWPCB.PPT
./clients/client455/~dmtmp/PWRPNT/PPTB1E4.TMP failed (Socket is not
connected) - expected NT_STATUS_OK
ERROR: child 455 failed at line 710
[808] open ./clients/client482/~dmtmp/PWRPNT/PPTC112.TMP failed for
handle 10042 (Socket is not connected)
[811] unlink ./clients/client161/~dmtmp/PWRPNT/PPTC112.TMP failed
(Socket is not connected) - expected NT_STATUS_OK
ERROR: child 161 failed at line 811
(809) ERROR: handle 10042 was not found

then trying `ls /mnt/mfs`:
# ls /mnt/mfs
ls: .: Socket is not connected

It`s normal behaviour or can be tuned?

Thanks.

----------------------------------------------------------------------------
--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
moosefs-users mailing list
moo...@li...
https://lists.sourceforge.net/lists/listinfo/moosefs-users