Impossible to back up on a CIFS sharing from Android

Status
Not open for further replies.
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

I am new in FreeNAS. I am using FreeNAS-9.3-STABLE-201601181840.iso.

I have created an user and a group to back up all the photos and videos from my Android mobile to the NAS. I created a Windows (CIFS) sharing on /mnt/vol1/Backup with the Wizard, owned by my user.

I am using Sweet Home! app in the mobile, which copies a given folder of the mobile to the Backup folder in the NAS.

Sweet Home begins to copy the photos without any problem, but suddenly, it stops with an error:

Code:
IMG_20150725_19704.jpg - FAILED (jcifs.smb.SmbException: Transport1 timedout waiting for response to SmbComWriteAndX[command=SMB_COM_WRITE_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=35129,uid=14390,mid=19213,wordCount=14,byteCount=15055,andxCommand=0xFF,andxOffset=0,fid=61128,offset=4703538,writeMode=0,remaining=0,dataLength=15054,dataOffset=64]


In FreeNAS I get the following:

Code:
Jan 25 06:17:15 freenas smbd[41179]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_89 (ipv4:192.168.0.164:51331) closed connection to service Backup
Jan 25 06:18:00 freenas smbd[41297]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_df (ipv4:192.168.0.164:49850) closed connection to service Backup
Jan 25 06:18:36 freenas smbd[41299]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_1d (ipv4:192.168.0.164:41692) closed connection to service Backup
Jan 25 06:19:40 freenas smbd[41346]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to fetch record!
Jan 25 06:33:34 freenas smbd[41825]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_1d (ipv4:192.168.0.164:50696) closed connection to service Backup
Jan 25 06:38:27 freenas smbd[42677]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_a1 (ipv4:192.168.0.164:49775) closed connection to service Backup
Jan 25 06:38:44 freenas manage.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint,name
Jan 25 06:38:56 freenas manage.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint,name
Jan 25 06:43:29 freenas smbd[42844]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_a1 (ipv4:192.168.0.164:40334) closed connection to service Backup
Jan 25 06:50:47 freenas smbd[43205]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsjcifs0_1_a1 (ipv4:192.168.0.164:48805) closed connection to service Backup


My smb4.conf is here:

http://pastebin.com/w5yvAYRd

As it can be seen, I disabled "Local Master" and "Hostnames lookups", as I saw in other posts, but the problem stills occurs.

What am I doing wrong? It is completely impossible to backup the 4000 files I want. The transfer stops every 4-5 photos... It is crazy...

If I share a folder in a Windows 7 and use Sweet Home! to back up there the photos, there is no problem at all. There must be a problem with Samba in FreeNAS or its configuration.

Thanks a lot.
 
DrKK

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
I do precisely what you describe. Exactly.

My method is I have installed "Foldersync Lite" on the Android phone, and I have used their "WebDAV" interface to the FreeNAS. Works like a charm. You will, of course, have to set up the WebDAV service on your FreeNAS, but that is very simple.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Thanks for the advice, DrKK.

I tried "Foldersync Lite" with the same CIFS sharing, and it goes a little better. Well, I mean, it does not close the connection, as "Sweet Home!" was doing, but, it stills stalls every couple of photos for a while (even seconds!), goes on, stalls, goes on... It is crazy, so sloooooow, but at least the transfer was not aborted.

I even tried https://forums.freenas.org/index.php?threads/cifs-directory-browsing-slow-try-this.27751/

Code:
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no


Really, what is the problem with Samba and FreeNAS? I thought it was quite mature... I never had a problem with a native Windows 7 sharing or dealing with a Synology.

This erratic behaviour makes FreeNAS not an operational solution for me, where almost all clients are Windows or Android devices...

I hope it is fixed soon, since I love the idea of having ZFS.
 
Last edited:
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Thanks for the advice, DrKK.

I tried "Foldersync Lite" with the same CIFS sharing, and it goes a little better. Well, I mean, it does not close the connection, as "Sweet Home!" was doing, but, it stills stalls every couple of photos for a while (even seconds!), goes on, stalls, goes on... It is crazy, so sloooooow, but at least the transfer was not aborted.

I even tried https://forums.freenas.org/index.php?threads/cifs-directory-browsing-slow-try-this.27751/

Code:
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no


Really, what is the problem with Samba and FreeNAS? I thought it was quite mature... I never had a problem with a native Windows 7 sharing or dealing with a Synology.

This erratic behaviour makes FreeNAS not an operational solution for me, where almost all clients are Windows or Android devices...

I hope it is fixed soon, since I love the idea of having ZFS.
Click to expand...
Samba in freenas is perfectly stable. You probably just need to properly configure permissions. Use 'system' -> 'advanced' -> 'save debug' to generate a debug tarball and post it here.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

Thank you for your interest. I appreciate it.

I am attaching the debug tarball and the console in a txt.

I noticed something quite interesting:

If the Sweet Home! app stays on foreground, it gets stalled while uploading, continues, takes a small pause, continues again, and finally stops with a jcifs.smb.SmbException like the one I put in the first post.

But, if I start uploading the photos, and change to Twitter and begin to browse downwards or I watch a video (while Sweet Home is on background), the transfer does not stop! o_O

So, I bet that the Samba client of the application is too fast for the Samba Server of FreeNAS...

But, before having this FreeNAS server, I was uploading my photos with the same app to a folder shared in Windows 7 and a Synology without any problem... and really fast.

Thanks again for studying this issue.
 

Attachments

  • debug-freenas-20160126210452..tgz
    311.3 KB · Views: 247
  • Console.txt
    39.6 KB · Views: 349
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Post the contents of /etc/local/smb4.conf

Additionally, under 'services' -> 'CIFS' increase logging level to "standard". Then reproduce the problem. While reproducing the problem run the command "smbstatus" and post the output here as well as /var/log/samba4/log.smbd.

Once you have done these steps reduce the logging level.
 
Last edited:
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Here is the /usr/local/etc/smb4.conf

Code:
[global]
    server max protocol = SMB2
    encrypt passwords = yes
    dns proxy = no
    strict locking = no
    oplocks = yes
    deadtime = 15
    max log size = 51200
    max open files = 220079
    load printers = no
    printing = bsd
    printcap name = /dev/null
    disable spoolss = yes
    getwd cache = yes
    guest account = nobody
    map to guest = Bad User
    obey pam restrictions = yes
    directory name cache size = 0
    kernel change notify = no
    panic action = /usr/local/libexec/samba/samba-backtrace
    nsupdate command = /usr/local/bin/samba-nsupdate -g
    server string = FreeNAS Server
    ea support = yes
    store dos attributes = yes
    lm announce = yes
    time server = yes
    acl allow execute always = true
    acl check permissions = true
    dos filemode = yes
    multicast dns register = yes
    domain logons = no
    local master = no
    idmap config *: backend = tdb
    idmap config *: range = 90000001-100000000
    server role = standalone
    netbios name = FREENAS
    workgroup = WORKGROUP
    security = user
    pid directory = /var/run/samba
    create mask = 0666
    directory mask = 0777
    client ntlmv2 auth = yes
    dos charset = CP437
    unix charset = UTF-8
    log level = 1
    ea support = no
    store dos attributes = no
    map archive = no
    map hidden = no
    map readonly = no
    map system = no


[BTSync]
    path = /mnt/vol1/BTSync
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Backup]
    path = /mnt/vol1/Backup
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Documents]
    path = /mnt/vol1/Documents
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Pics]
    path = /mnt/vol1/Pics
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[prueba]
    path = /mnt/vol1/prueba
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare
 
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Here is the /usr/local/etc/smb4.conf

Code:
[global]
    server max protocol = SMB2
    encrypt passwords = yes
    dns proxy = no
    strict locking = no
    oplocks = yes
    deadtime = 15
    max log size = 51200
    max open files = 220079
    load printers = no
    printing = bsd
    printcap name = /dev/null
    disable spoolss = yes
    getwd cache = yes
    guest account = nobody
    map to guest = Bad User
    obey pam restrictions = yes
    directory name cache size = 0
    kernel change notify = no
    panic action = /usr/local/libexec/samba/samba-backtrace
    nsupdate command = /usr/local/bin/samba-nsupdate -g
    server string = FreeNAS Server
    ea support = yes
    store dos attributes = yes
    lm announce = yes
    time server = yes
    acl allow execute always = true
    acl check permissions = true
    dos filemode = yes
    multicast dns register = yes
    domain logons = no
    local master = no
    idmap config *: backend = tdb
    idmap config *: range = 90000001-100000000
    server role = standalone
    netbios name = FREENAS
    workgroup = WORKGROUP
    security = user
    pid directory = /var/run/samba
    create mask = 0666
    directory mask = 0777
    client ntlmv2 auth = yes
    dos charset = CP437
    unix charset = UTF-8
    log level = 1
    ea support = no
    store dos attributes = no
    map archive = no
    map hidden = no
    map readonly = no
    map system = no


[BTSync]
    path = /mnt/vol1/BTSync
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Backup]
    path = /mnt/vol1/Backup
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Documents]
    path = /mnt/vol1/Documents
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[Pics]
    path = /mnt/vol1/Pics
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare


[prueba]
    path = /mnt/vol1/prueba
    printable = no
    veto files = /.snapshot/.windows/.mac/.zfs/
    writeable = yes
    browseable = yes
    vfs objects = zfs_space zfsacl aio_pthread streams_xattr
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = true
    zfsacl:acesort = dontcare
Click to expand...
Under 'services' -> 'CIFS' increase logging level to "standard". Then reproduce the problem. While reproducing the problem run the command "smbstatus" and post the output here as well as /var/log/samba4/log.smbd.

Once you have done these steps reduce the logging level.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

Here is the output of smbstatus during the transfer and just after it was aborted:

Code:
[root@freenas] ~# smbstatus

Samba version 4.1.21
PID     Username      Group         Machine
-------------------------------------------------------------------
19540     mida          family        192.168.0.164 (ipv4:192.168.0.164:51016)
19540     mida          family        192.168.0.164 (ipv4:192.168.0.164:51016)

Service      pid     machine       Connected at
-------------------------------------------------------
Backup       19540   192.168.0.164  Tue Jan 26 22:26:37 2016
Backup       19540   192.168.0.164  Tue Jan 26 22:26:41 2016

Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Locked files:
Pid          Uid        DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
19540        1001       DENY_NONE  0x8b        RDWR       NONE             /mnt/vol1/Backup   MovilDario/Camera/IMG_20151222_094431.jpg.tmp   Tue Jan 26 22:26:57 2016

[root@freenas] ~# smbstatus

Samba version 4.1.21
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------

Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No locked files

[root@freenas] ~# ls


And the /var/log/samba4/log.smbd

Thanks!
 

Attachments

  • log.smdb.zip
    12.7 KB · Views: 242
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I use FolderSync like DrKK. It works well. Sweet Home! should work (assuming it follows proper CIFS protocol). I will say that sending your backups over wifi is going to be slow and intermittent. Wifi just kind of sucks, and that's the way it is. The good news is that if you set it to run at 2AM or whenever you sleep, it should finish without problems. I do my backups at 2AM for just this reason. ;)
 
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Hi.

Here is the output of smbstatus during the transfer and just after it was aborted:

Code:
[root@freenas] ~# smbstatus

Samba version 4.1.21
PID     Username      Group         Machine
-------------------------------------------------------------------
19540     mida          family        192.168.0.164 (ipv4:192.168.0.164:51016)
19540     mida          family        192.168.0.164 (ipv4:192.168.0.164:51016)

Service      pid     machine       Connected at
-------------------------------------------------------
Backup       19540   192.168.0.164  Tue Jan 26 22:26:37 2016
Backup       19540   192.168.0.164  Tue Jan 26 22:26:41 2016

Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Locked files:
Pid          Uid        DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
19540        1001       DENY_NONE  0x8b        RDWR       NONE             /mnt/vol1/Backup   MovilDario/Camera/IMG_20151222_094431.jpg.tmp   Tue Jan 26 22:26:57 2016

[root@freenas] ~# smbstatus

Samba version 4.1.21
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------

Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No locked files

[root@freenas] ~# ls


And the /var/log/samba4/log.smbd

Thanks!
Click to expand...
It appears that permissions are set properly. Your phone is authenticating using the correct credentials. I think that your phone's smb client is buggy. Perhaps use a different app. log.smbd doesn't give an indication where the foul-up is happening.

If the problem persists, increase logging level to "full" then post /var/log/samba4/log.smbd.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

Here is the log.smdb at Full.

The IMG_20151222_094431 was correctly uploaded.

The IMG_20151222_094506 failed.

The exception in the app was:

Code:
IMG_20151222_094506.jpg - FAILED (jcifs.smb.SmbException: Transport1 timedout waiting for response to SmbComWriteAndX[command=SMB_COM_WRITE_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0C8803,signSeq=0,tid=26368,pid=15285,uid=7818,mid=5813,wordCount=14,byteCount=16575,andxCommand=0xFF,andxOffset=0,fid=1026,offset=2851956,writeMode=0,remaining=15054,dataLength=16574,dataOffset=64]
 

Attachments

  • log.smbd.zip
    153.1 KB · Views: 263
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Hi.

Here is the log.smdb at Full.

The IMG_20151222_094431 was correctly uploaded.

The IMG_20151222_094506 failed.

The exception in the app was:

Code:
IMG_20151222_094506.jpg - FAILED (jcifs.smb.SmbException: Transport1 timedout waiting for response to SmbComWriteAndX[command=SMB_COM_WRITE_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0C8803,signSeq=0,tid=26368,pid=15285,uid=7818,mid=5813,wordCount=14,byteCount=16575,andxCommand=0xFF,andxOffset=0,fid=1026,offset=2851956,writeMode=0,remaining=15054,dataLength=16574,dataOffset=64]
Click to expand...
Out of curiousity, try setting "strict allocate = yes" as an auxiliary parameter for your backups share.

Does the CIFS client app let you adjust the timeout values? If so, increase the value. It might be a combination of wireless connection and the realtek NIC you have in the server (and whatever networking hardware you have in between). The jcifs client seems to be issuing a ton of smbwritex commands almost simultaneously. They might be overwhelming your server and causing timeouts. Realtek NICs aren't well known for their performance under load, but wireless can also be quite terrible. There's lots of room for blame all around.
 
Last edited:
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

I have just tried with the "strict allocate = yes" auxiliary parameter in the Backup sharing and it is the same. It gets stalled from time to time until it finally stops. I am attaching the log.

The LAN chip is the Realtek RTL8111GR. I do not know how well it is supported in FreeNAS. How often are the drivers updated? Every major/minor version or more often?

Well, I will try uploading other family's photos with FolderSync and let's hope it works better.

Thanks!
 

Attachments

  • log.smbd.zip
    231.4 KB · Views: 253
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Hi.

I have just tried with the "strict allocate = yes" auxiliary parameter in the Backup sharing and it is the same. It gets stalled from time to time until it finally stops. I am attaching the log.

The LAN chip is the Realtek RTL8111GR. I do not know how well it is supported in FreeNAS. How often are the drivers updated? Every major/minor version or more often?

Well, I will try uploading other family's photos with FolderSync and let's hope it works better.

Thanks!
Click to expand...
Remove the "strict allocate = yes" parameter. You can try increasing logging to "debug" then reproduce the problem, but my gut-feeling is that it won't show much more than is already in the log. If the NIC is part of the problem, which is probably the case, then the best solution is to buy an Intel gigabit NIC. They can typically be had for around $30.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.

Here is the log (cut into four pieces) for uploading a video from the mobile with Sweet Home.

Ah, I found a great wraparound: open YouTube in the mobile with the best 50 videos of the year while, on the background, the photos are uploaded to the NAS :D

Well, if it is due to the NIC, I'll have to buy a EXPI9301CTBLK or EXPI9301CT card. Are they ok?

Thanks again.
 

Attachments

  • log_1.zip
    466.8 KB · Views: 232
  • log2.zip
    1.8 MB · Views: 273
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
And 3rd, 4th and 5th pieces.
 

Attachments

  • log3.zip
    867.6 KB · Views: 259
  • log4.zip
    1.5 MB · Views: 256
  • log5.zip
    1.4 MB · Views: 313
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
darioml said:
Hi.

Here is the log (cut into four pieces) for uploading a video from the mobile with Sweet Home.

Ah, I found a great wraparound: open YouTube in the mobile with the best 50 videos of the year while, on the background, the photos are uploaded to the NAS :D

Well, if it is due to the NIC, I'll have to buy a EXPI9301CTBLK or EXPI9301CT card. Are they ok?

Thanks again.
Click to expand...
That NIC will do fine.
It's still hard for me to say what's going on. It looks like the client is trying to use aio for writes. It's also writing NTFS alternate datastreams as its going (calling streams_xattr_pwrite). There are hard limits on how large an ADS can be in samba.

Perhaps try the following auxiliary parameter for your backups share:
"aio write size = 1"
The above parameter will force all write IO to the share be AIO.
Also remove the "aio_pthread" vfs object. This will force samba to use the pthread based AIO path that's baked into samba. By default, the code path the client is trying to use is disabled (aio write size is set to 0).

If this doesn't help with the backup task, try removing the "streams_xattr" vfs object. I'd make sure the app is entirely stopped between each modification so that you don't end up with a stale session mucking things up.
 
D

darioml

Dabbler
Joined
Oct 10, 2015
Messages
20
Hi.
Perhaps try the following auxiliary parameter for your backups share:
"aio write size = 1"
The above parameter will force all write IO to the share be AIO.
Also remove the "aio_pthread" vfs object. This will force samba to use the pthread based AIO path that's baked into samba. By default, the code path the client is trying to use is disabled (aio write size is set to 0).
Click to expand...

I am attaching the log cut in 5 pieces. Please, rename them to log.zip.001 to log.zip.005 to extract the original log.smdb.

I noticed, from the user side, that it is slightly more stable: the transfer seems to be aborted later than before. But, maybe at low level, the change is not so significant.

If this doesn't help with the backup task, try removing the "streams_xattr" vfs object. I'd make sure the app is entirely stopped between each modification so that you don't end up with a stale session mucking things up.
Click to expand...

I will try this tonight.

Thanks!
 

Attachments

  • log.zip.001.zip
    1 MB · Views: 225
  • log.zip.002.zip
    1 MB · Views: 250
  • log.zip.003.zip
    1 MB · Views: 313
  • log.zip.004.zip
    1 MB · Views: 241
  • log.zip.005.zip
    234.3 KB · Views: 236
  • smb4.zip
    1 KB · Views: 227
Status
Not open for further replies.

Similar threads

dziring
  • Locked
SOLVED Recurring message in log
Replies
1
Views
1K
dziring
dziring
Brentnall
  • Locked
Samba information messages logged as Errors?
Replies
2
Views
1K
Brentnall
Brentnall
Skyfox
  • Locked
Odd samba entries in the FreeNAS log
Replies
7
Views
2K
anodos
anodos
Paranoiak
  • Locked
Can it really be considerated as an ERROR ?
Replies
2
Views
913
Paranoiak
Paranoiak
I
  • Locked
Samba error with CIFS share
Replies
4
Views
4K
insomnium
I
Top