SeaDrive stuck on file "Creating partial commit"

seadrive

#1

I’m on Ubuntu 16.04 using the headless SeaDrive client version 0.9.2.

Very often it happens that SeaDrive gets stuck on indexing. The result in the logs looks like this

[05/24/18 08:27:13] sync-mgr.c(2378): Failed to index file item_100/file_100.pdf in repo 3783c59d-9548-43bc-9b6c-1c6173a56720, skip.
[05/24/18 08:27:13] sync-mgr.c(2612): Creating partial commit after adding item_101/item_101.pdf in repo orders-live-th(3783c59d).
[05/24/18 08:27:14] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'committing' to 'synchronized'.
[05/24/18 08:27:14] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'synchronized' to 'committing'.
[05/24/18 08:27:14] cdc.c(166): File size changed while chunking.
[05/24/18 08:27:14] fs-mgr.c(376): Failed to chunk file with CDC.
[05/24/18 08:27:14] sync-mgr.c(2378): Failed to index file item_100/file_100.pdf in repo 3783c59d-9548-43bc-9b6c-1c6173a56720, skip.
[05/24/18 08:27:14] sync-mgr.c(2612): Creating partial commit after adding item_101/item_101.pdf in repo orders-live-th(3783c59d).
[05/24/18 08:27:15] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'committing' to 'synchronized'.
[05/24/18 08:27:15] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'synchronized' to 'committing'.

So it prints

Creating partial commit after adding item_101/item_101.pdf in repo orders-live-th(3783c59d).

over and over again and consumes alot of CPU.

After moving the file to another location, it prints

[05/24/18 08:29:20] file-cache-mgr.c(2182): Failed to stat /opt/seadrive/seadrive-data/file-cache/3783c59d-9548-43bc-9b6c-1c6173a56720/item_101/item_101.pdf: No such file or directory.
[05/24/18 08:29:20] sync-mgr.c(2378): Failed to index file item_101/item_101.pdf in repo 3783c59d-9548-43bc-9b6c-1c6173a56720, skip.
[05/24/18 08:29:20] sync-mgr.c(2612): Creating partial commit after adding item_100/file_100.pdf in repo orders-live-th(3783c59d).
[05/24/18 08:29:20] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'committing' to 'synchronized'.
[05/24/18 08:29:21] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'synchronized' to 'committing'.
[05/24/18 08:29:21] file-cache-mgr.c(2182): Failed to stat /opt/seadrive/seadrive-data/file-cache/3783c59d-9548-43bc-9b6c-1c6173a56720/item_101/item_101.pdf: No such file or directory.
[05/24/18 08:29:21] sync-mgr.c(2378): Failed to index file item_101/item_101.pdf in repo 3783c59d-9548-43bc-9b6c-1c6173a56720, skip.
[05/24/18 08:29:21] sync-mgr.c(2612): Creating partial commit after adding item_100/file_100.pdf in repo orders-live-th(3783c59d).
[05/24/18 08:29:21] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'committing' to 'synchronized'.
[05/24/18 08:29:22] sync-mgr.c(570): Repo 'orders-live-th' sync state transition from 'synchronized' to 'committing'.

Then after moving the other files which are giving “Creating partial commit after adding” and waiting some minutes, SeaDrives starts to work again normally.


#2

Is “item_101/item_101.pdf” the actual name of the file? If so, it has the “/” in it and that is a reserved character not meant for filenames. Changing the filename should solve the problem.


#3

No, its a directory item_101 with a file item_101.pdf


#4

Could you download, rename and reupload the file to SeaFile? How large is the file? Are you using Pro or CE? Seems SeaFile is working very hard on indexing the file. Could it also be possible that changes were made during the index of the file?


#5

There seems to be no pattern. It happens over and over again on different files. After moving the file to another location and waiting for seadrive to normalize and then moving the file back to seadrive, it works normally.

I use CE. Reuploading the file works without problem. The files have different sizes. Some are 10 MB, others are 200 MB. My guess is, that another program is accessing the files and maybe seadrive gets screwed then. I have FTP, Webserver and a PDF preview application running.


#6

This is what I thought, too. But SeaFile stores his data in the hashed blocks. Have you SeaFUSE enabled or can any other Service Acces the Files? Are the files randomly?


#7

The files are random. I use SeaDrive, I guess internally its working with Fuse to provide the files. Other application have access to the files too. SeaFile wasnt making such problems back then. It started when I switched to SeaDrive.


#8

No I ment some other applications on other Computers/the server. But could it be possible that a programm is always changing the files or a the really completely randomly?


#9

Well it might be that the file is changing during indexing, but isnt it a bug then? I mean SeDrive should reindex then,


#10

You can reproduce a similar issue with the client, but you hardly get it, even if you try to get it. Seems there the protocol crashes when it’s syncing during a index. The way to prevent this would be just index files who appeared at the beginning of the index Process. Could be something for future.
At the moment, SeaDrive is still beta, so errors will occur. The only way is to reinstall.


#11

Sure. Thats why I write this here. Hopefully the devs find some time to fix it.


#12

Nobody knows what they really want to do with SeaDrive. Maybe it’s closed source because Dropbox tried to fake it in first time and others want to have such a feature, so that they will be the only ones with such feature. Or they want people to pay for pro when it’s ready for release. Or they want sell the technology. But for all options they should have a dev team what always works on it, but they don’t. And the community can’t help because it isn’t open source. That’s the problem and that’s why nobody can help to solve most SeaDrive issues.


#13

This is definitely not the case.


#14

Just guessing


#15

I noticed this happens, when the CPU usage of the server is high. Maybe its related.


#16

Of course it’s related, because it’s caching lots of files.