SMB Sync multiple users

[thechonta]

Server configuration

Operating system:Ubuntu 18.04 Web server:Apache 2.4.29 Database:mariadb Ver 15.1 PHP version:7.2.15 Nextcloud version:15.0.7 Desktopclient 2.5.0++ Client OS:Windows 10/ Windows 7 **SMB Server 2016

The issue you are facing:

Is this the first time you’ve seen this error? (Y/N): N

Hello together. Given is an nextcloud updated to 15.0.7 on an Ubuntu 18.04 up to date and smbclient Version of 4.9.5 because auf troble of Notification SMB in the 4.7.X version that comes with Ubuntu but the following problem is regardless of that.

Userbackend is LDAP (AD) on an Server 2016. It is used the external_store SMB/CIFS with logindata saved in Database. In the Store is Accessenumeration active, the share has a lot of sub folders.

All Users uses the Nextcloud Desktop client. User A changes an File on the Share on first Level the on the Desktop the File Changes will be submitted to User B as well. User A changes an File though web-browser (even txt) the changes only submitted to user A, user B has to open the file in the browser or to visit the folder of the file in the browser, than it will be synced to the computer.

User A changes an file or create an file in an subfolder, no changes will be noticed for user B. If user B browses to the file, than it will be synced.

The expected behavior is, that user A changes an file or creates something on the share (per client or browser), user B will sync the data to his desktop as well. A view minutes after i was upgrading from 15.0.4 to 15.0.7 it worked like this but than all of a sudden it stopped working. There no errors in the Logfiles of the nextcloud so far.

If the share set up with username and password saved in the nextcloud, than it works. But than the accessenumeration on the fileserver could not be used. Because the fact, that changes on the first level got noticed, as log as it was initiated per client are synced, shows that it should work also for subfolder as well. The nextcloud should know what file was changed and provide the clients the information so the clients can check the backend store.

Is there a workaround to force the clients to checkup the store for changes?

Thank you for help.

[thechonta]

UPDATE

 sudo -u www-data  php -f /var/www/nextcloud/occ files:scan -vv --unscanned

no changes if there are som cahnges

 sudo -u www-data  php -f /var/www/nextcloud/occ files:scan --all

This will trigger changes but only if

/data/nextcloud_data/user/files/

is Writable. Is there an Possible Option to trigger this also if

/data/nextcloud_data/user/files/

is not writable? Or only trigered to Shares for the User? The reason why

/data/nextcloud_data/user/files/

is not writable is to prevent Datastorage by the user other than the Filservershare.

[thechonta]

Any new information from someone with programming knowledge? :-)

[CommonBlob]

We have had this problem since v10 of Nextcloud. The way we got around it was to manually sync, in a cron job, the folders we suspected people were syncing using files:scan -path. Not great. We have never got the notify job to successfully run. Its becoming likely that we will move solutions.

Furthermore, while testing notify using smbclient it works as expected. It just doesn't work via Nextcloud 16.0.1

[thechonta]

Some good news about a fix for that?

[thechonta]

I need a Hero with coding skills :-)

[thechonta]

Since Nextcloud 10 it is a serios Problem, why is nor one helping? If ther would be bought an Nextcloudsubscription how long will it tage this problem will be fixed? Our is an subscription not a gurantee to get problems you have fixed?

[ariselseng]

@thechonta I think you are better off contacting nextcloud gmbh directly or maybe add some funding for this on bountysource.

[torstensson]

This issue has not been solved and should not be labeled stale in my opinion

[kesselb]

This issue has not been solved and should not be labeled stale in my opinion

Yep. Forgot to remove the "needs info" label :see_no_evil:

I also have some new (at least for me) information about this topic: https://github.com/nextcloud/server/issues/16834#issuecomment-525334992. Not a fix or a workaround but some additional context.

[kesselb]

cc @nextcloud/server-triage If I understand this issue correctly then smb shares with user credentials does not inform each other about changes. Every user share is a own share and there is not a connection between the shares (even if they access the same storage). This leads to the situation that oc_filecache is huge (e.g. #16834). Is this a topic on your roadmap?

[blizzz]

I don't think so. Maybe @icewind1991 knows more.

[thechonta]

PUSH, 01.03.2021. External Share on Windows Fileserver as an Example, Access by Logindata saved in Database. Sextcloud Server 21.0.0 including the new notify_push....... nextcloud desktopclient 3.1.3

User 1 Changes or even Add an File on the 4th subdiectory user 2 with the same access to the same external share will get no information about changed data.

Changes on the Fileserver itself are not Rcognized, sad bu undersandable, but the Access of the folder over Webbrowser always shows the actual Data, why not sending Folderlist request also over the Desktopclient to get actual Data? If i change an File on the Desktopclient the changed File on the Server are ignored! BUT if i add a new file, the file that was changed on the Fileserver directly will be actualized on the client side.

User 2 will not be aware of any of this!

If user 2 add a new File he will also get all the missing Information but probably overwrite informations if files of him had the same name like files of user 1....

The changing of information on user does are in the database of the server (at least should be) and the server has to inform all client that have access to a resource about changes in that resource so all have the same data.

what works perfectly with local disk of the server does not relay work with external shares (sad) I was hoping the new notify_push would deal with this problem, but no...

[szaimen]

This looks like a duplicate of https://github.com/nextcloud/server/issues/23988 to me...

[ghost]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[XTC-Desperado]

Have a look here https://apps.nextcloud.com/apps/files_inotify and all attachments to it. For the use of a Nextcloud client on the PC, this is mandatory and also has restrictions depending on the number of folders/files. In the browser and on the smartphone app, inotifiy is not necessary because the session actively looks in live when it is called up. The Nextcloud client works differently, regardless of whether with virtual folders or in the offline cache - at the beginning it works, when using the "client" it always works because the client actively plays along. If a user B changes something on the external SMB share, the Nextcloud server doesn't notice - logical, that's why files_innotify. Or make a request to build a function into the Nextcloud client so that it does a "resync", but I think this is impractical for "end users", dangerous and takes too long depending on the amount of data. Here's a challenge for personal home drives "Servername; /home ;/$user ;MyDomain" https://github.com/nextcloud/documentation/commit/32241b66935d135e1540c7e7beccbfdb0ed92323

German: Schau mal hier rein https://apps.nextcloud.com/apps/files_inotify und alle Anhängigkeiten dazu. Für die Benutzung eines Nextcloud-Clients auf dem PC ist das zwingend notwendig und hat auch je nach Einschränkungen je nach Anzahl Ordner/Dateien. Im Browser und auf per Smartphone-App ist inotifiy nicht nötig, da die Sitzung beim Aufruf da aktiv live reinschaut. Der Nextcloud-Client funktioniert anders, egal ob mit virtuellen Ordnern oder im Offline-Cache - am Anfang klappts, bei der Nutzung des "Clients" geht´s auch immer, weil der Client aktiv mitspielt. Wenn ein User B auf dem externen SMB-Share etwas ändert, bekommt Nextcloud-Server davon nichts mit - logisch, deswegen files_innotify. Oder nen Request machen, ob man in Nextcloud-Client da eine Funktion einbaut, das der einen "Resync" macht, halt ich aber für "Endanwender" unpraktikabel, gefährlich und dauert je nach Datenmenge zu lange. Hier mal eine Herausforderung für persönliche Homelaufwerke "Servername; /home ;/$user ;MyDomain" https://github.com/nextcloud/documentation/commit/32241b66935d135e1540c7e7beccbfdb0ed92323