Deduplicate blocks between libraries as option

210 views
Skip to first unread message

Sz Gy

unread,
Mar 24, 2014, 2:06:40 PM3/24/14
to sea...@googlegroups.com
Hi!

I read recently in Roadmap  (https://seacloud.cc/group/3/wiki/seafile-roadmap-3-x/) that "Do not deduplicate blocks between libraries. Libraries will be separate from each other."

I like the feature to deduplicate between libraries. Could you please let it configurable?

I like it because I have limited storage and many times I share the some content in many libraries. I do not want to make additional libraries for groups for commonly shared videos, pictures and so on...

Lingtao Pan

unread,
Mar 25, 2014, 9:06:37 AM3/25/14
to sea...@googlegroups.com
Do you mean you have the same contents in different libraries?

Sz Gy

unread,
Mar 25, 2014, 12:14:38 PM3/25/14
to sea...@googlegroups.com
Yes.

There are content I like to share with group A and group B but there are a lot of content I like to share just with group A.

I mean:

There are a library groupA and a library groupB. Lib.groupA is configured in groupA's PC and Lib.groupB is configured in groupB's PC. So I basically need just 2 shares each for client. I upload the overlapping content in to both share / library. It's fast (after the initial upload the second is just some kind of checksumming:) and requires no additional space. And a lot better than educating clients that from now on you have to look for content like pictures or videos in two different directory. :)

So please keep the deduplication between libraries too...

Lingtao Pan

unread,
Mar 25, 2014, 10:05:51 PM3/25/14
to sea...@googlegroups.com
We can't keep deduplication between libraries.

However you can achieve your goal by using two sub-libraries. Just merge these two libraries into a single library with two directories.


--
You received this message because you are subscribed to a topic in the Google Groups "seafile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/seafile/Y5xfuBGjnRc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to seafile+u...@googlegroups.com.
To post to this group, send email to sea...@googlegroups.com.
Visit this group at http://groups.google.com/group/seafile.
For more options, visit https://groups.google.com/d/optout.

Sz Gy

unread,
Mar 26, 2014, 3:10:29 AM3/26/14
to sea...@googlegroups.com
You are right. Thanks!

Kristian Grizelj

unread,
Mar 26, 2014, 10:53:34 AM3/26/14
to sea...@googlegroups.com
I am very disappointed with the new option, "Do not deduplicate blocks between libraries."
Not a problem only data storage, but if I want to send my colleague 200MB difrent library that will last an hour (upload speed 50KB/s). Each share will require reupload data that already exist on the server.
The main feature of the sync-Cloud, is the speed and to minimize the flow of data. And that's the example Dropbox leader.
The point is, solve problems, and do not turn off the core functions. Top excluded completely deduplication and no problem with cash, clean copy-paste and during the upload that the file is locked like Owncloud.

Kristian Grizelj

unread,
Mar 26, 2014, 11:24:58 AM3/26/14
to sea...@googlegroups.com

The first time I tested Seafile ver 2.0.4 was enthusiastic to great works. Perfectly Super.
Then I discovered that there is no "Preserver file timestamp during syncing" (I waited but was postponed three times). Indexing, does not bother me at first indexing, but after changes one letter causes make completely re-indexing library.
Delta file, deduplication does not work after a reboot seafile client (cash delete blocks) and when small changes file at work, come home and redownload the Whole file.
Definitely sure you have a superior product, my congratulations, and I waited only "Preserve file timestamp" and is great options "Allow setting of sync interval for a library"

Lingtao Pan

unread,
Mar 28, 2014, 4:36:46 AM3/28/14
to sea...@googlegroups.com
Why "Each share will require reupload data that already exist on the server"? You may mis-understanding what library deduplicating mean.

Preserve file timestamp is already done in version 3.0

Lingtao Pan

unread,
Mar 28, 2014, 4:36:57 AM3/28/14
to sea...@googlegroups.com
Why "Each share will require reupload data that already exist on the server"? You may mis-understanding what library deduplicating mean.

Preserve file timestamp is already done in version 3.0


On Wednesday, 26 March 2014 22:53:34 UTC+8, Kristian Grizelj wrote:

Kristian Grizelj

unread,
Mar 31, 2014, 2:36:05 PM3/31/14
to sea...@googlegroups.com
Thank you for your attention Lingtao
If I have my library and another library that I share with, for example, my wife and I Copy 200MB files
with pictures it will cause reupload whole 200MB on my upload speed of 50K/B it will take one hourr, because it's another library, not deduplication.

YesI have seen that you realize Preserve file timestamp in version 3.0" (very very important to me, as if someone removed the dates with e-Mails) and Do not automatically unsync a library and Allow setting of sync interval for a library .
All the great features.

Thank you very much for that

Kristian Grizelj

unread,
Mar 31, 2014, 2:53:35 PM3/31/14
to sea...@googlegroups.com
I know that everyone has something important to me is important not to make mistakes, accidental erasure..... !, And to transfer as little data if possible (deduplication).
Client works fabulously when uploading data, I change the name of the folder with 10GB of data, indexing, and in a few seconds it's over. Super.
The problem is when downloading after reboot Client (clear chunk blocks).
Client thereafter and regular change of folder names redownload whole folder with 10GB of data, which at speeds of 50K / B lasts 55 hours.
Seafile client does not know that I have already identified those files and creates a chunk blocks and decided, okay I have 55 blocks and one I dont have, I just downloading this one.
and instead work from a few seconds works 55 hours
Reply all
Reply to author
Forward
0 new messages