From: Akhobadze A. <akh...@ri...> - 2015-04-16 10:45:35
|
Hi All! And what happens when you copy files from NetWare to some other drive type (NO to SAMBA-MooseFS) ? Does the error represent if not using SAMBA-MooseFS ? Where there is in Your opinion error occurs while reading from NetWare or while writing to SAMBA-MooseFS ? May be it is a good idea to mount NetWare volume directly on MooseFS client side and copy files without Windows ? Also You can try to copy files from Windows to MooseFS via ftp or sftp. --- > -----Original Message----- > From: Neddy, NH. Nam [mailto:na...@nd...] > Sent: Wednesday, April 08, 2015 12:01 PM > To: MooseFS Users > Cc: moo...@li... > Subject: Re: [MooseFS-Users] "An unexpected network error occurred" > > Hi Aleksander, > > On Samba (3.6.6) server, I switched to different protocols than > default but still no luck. > > client max protocol = LANMAN1 > > Also use option -o mfscachemode=NO but the result is the same. > > Best regards, > ~Nedd > > On Wed, Apr 8, 2015 at 2:58 PM, MooseFS Users <us...@mo...> > wrote: > > Hi. > > We have two ideas that you can test in your environment. > > > > First of all try to force SAMBA server to use only SMB2 or even SMB1 > > protocol. > > More details about configuration you can find at: > > www.samba.org/samba/history/samba-4.1.0.html > > > > Another idea is to disable caching in mfsmount: > > mfsmount -o mfscachemode=NO -H mfsmaster.lan /mount/point > > > > We are waiting for your feedback. > > > > Best regards > > Aleksander Wieliczko |