diff options
| author | neodarz <neodarz@neodarz.net> | 2017-04-28 00:30:19 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2017-04-28 00:30:19 +0200 |
| commit | 9a88e9ff0385f66e7c565a394908503dc6e916ad (patch) | |
| tree | 05ea8b356163f06c5fc99c2caf67fa8d3a28d67d /build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html | |
| parent | f1965c50670f611ef54f9471490d45a554f7d866 (diff) | |
| download | my_new_personal_website-9a88e9ff0385f66e7c565a394908503dc6e916ad.tar.xz my_new_personal_website-9a88e9ff0385f66e7c565a394908503dc6e916ad.zip | |
Site updated at 2017-04-28T00:29:42+02:00
source branch was at:
f1965c50670f611ef54f9471490d45a554f7d866 Correct a link
Diffstat (limited to 'build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html')
| -rw-r--r-- | build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html b/build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html new file mode 100644 index 00000000..bec8ebd5 --- /dev/null +++ b/build/blog/2014-10-28-google-drive-no-selective-subfolder-sync.html @@ -0,0 +1,63 @@ +<!DOCTYPE html> +<html> +<head> +<meta charset="utf-8"/> +<meta content="pandoc" name="generator"/> +<meta content="Zhiming Wang" name="author"/> +<meta content="2014-10-28T20:49:24-0700" name="date"/> +<title>Google Drive — no selective subfolder sync?</title> +<link href="/img/apple-touch-icon-152.png" rel="apple-touch-icon-precomposed"/> +<meta content="#FFFFFF" name="msapplication-TileColor"/> +<meta content="/img/favicon-144.png" name="msapplication-TileImage"/> +<meta content="width=device-width, initial-scale=1" name="viewport"/> +<link href="/css/normalize.min.css" media="all" rel="stylesheet" type="text/css"/> +<link href="/css/theme.css" media="all" rel="stylesheet" type="text/css"/> +</head> +<body> +<div id="archival-notice">This blog has been archived.<br/>Visit my home page at <a href="https://zhimingwang.org">zhimingwang.org</a>.</div> +<nav class="nav"> +<a class="nav-icon" href="/" title="Home"><!--blog icon--></a> +<a class="nav-title" href="/"><!--blog title--></a> +<a class="nav-author" href="https://github.com/zmwangx" target="_blank"><!--blog author--></a> +</nav> +<article class="content"> +<header class="article-header"> +<h1 class="article-title">Google Drive — no selective subfolder sync?</h1> +<div class="article-metadata"> +<time class="article-timestamp" datetime="2014-10-28T20:49:24-0700">October 28, 2014</time> +</div> +</header> +<p>Up to this point I've been using Google Drive as an online backup service, and uploads files mostly manually, although I do sync <code>~/img</code> with the client.</p> +<p><strong>Aside.</strong> Google Drive, OneDrive, etc. don't work with symlinks. Wanna keep your stuff free and duplicate-free yet still synced to the servers? Use <code>rsync</code> to automatically reproduce your folder structure with hard links:</p> +<pre><code>rsync -avzP --delete --link-dest=SOURCE/ SOURCE DESTINATION</code></pre> +<p>e.g.,</p> +<pre><code>rsync -avzP --delete --link-dest=~/img/ ~/img/ ~/sync/GoogleDrive/img/</code></pre> +<p>automatically reproduces my <code>~/img</code> in the <code>img</code> directory under Google Drive's root, yet every file in the <code>~/img</code> tree is replaced by hard links to the original file, so the new structure within Google Drive takes little additional space — for the directories only.</p> +<p>That doesn't solve every problem though, as you will see shortly. <em>End of aside.</em></p> +<p>So, up to this point I’ve mostly used Google Drive as an online backup service by manually uploading (huge) stuff. But at some point I’m gonna automate parts of the uploading. As it turns out, I can keep some smaller video files on my hard drive; other bigger monsters (like movies, TV shows, etc., especially a lot of 1080i Transport Streams directly from TV broadcasts) are uploaded and then moved to external drives. Some of the smaller files, including things downloaded from YouTube, live in <code>~/vid/etc</code>, and I want to sync this folder to Google Drive. What's shocking is that this is not possible with the Google Drive client — it only allows selective syncing of the top level folders. Let me repeat this:</p> +<p><strong>The Google Drive client only allows selective syncing of the <em>top level folders</em>.</strong></p> +<p>This is <em>insane</em>. It’s almost 2015. Everyone supports this — Dropbox, Microsoft, Box, even Baidu. Google Drive launched on April 24, 2012, that’s 2.5 years ago. <a href="https://productforums.google.com/forum/#!topic/drive/Gs2w1BL-B9U">This thread</a> on Google Drive Forum, “Ability to sync only selected sub folders”, was posted on August 27, 2012, and has garnered 139 replies. They are ignored by the developers, and the accepted “answer” is to utilize Google Drive’s assign-one-file/folder-to-multiple-folders feature to create a special “sync” directory. Okay, that’s a stupid hard link solution on the server side. Okay, if that works… <em>No</em>. “Hard links on the server side” cannot bear different names; so what if I want to sync, say, both <code>vid/etc</code> and <code>aud/etc</code>? Whoops. So I also have to do all sorts of ugly renaming. NO, GOOGLE, NO, I won't accept that much trouble.</p> +<p>This kind of insanity makes me wander:</p> +<p><strong>Do the Google Drive developers use Google Drive themselves?</strong></p> +<p>For now I'm moving <code>vid/etc</code> to <code>vid_etc</code>. Sigh.</p> +<hr/> +<p>There are other problems that I encountered with Google Drive sync today. For one thing, it rejects what I already have and insists on starting from scratch. I mean, say I have uploaded a folder via the web interface, and later wants to keep it in sync (of course that's only possible if it's top level), so I put what I already have there. Nope, Google Drive reports that as a conflict and insists on downloading all the stuff again. Apart from wasted traffic, that also ruins my hard links, so I have to either wipe everything clean on the server side and reupload, or redownload everything and redo all the hard-linking after the download finishes. Either way, very annoying. I opted for the first one. (I later empirically confirmed that OneDrive could handle this situation.)</p> +<p>There are other problems that don't pop right off my mind. Anyway, the gist is,</p> +<p><strong>Google Drive is not yet sync-ready for power users (maybe even laymen).</strong></p> +<hr/> +<p>Then, is OneDrive perfect? No. I know it recently went unlimited, but there’s one major annoyance: the speed. Stanford’s Ethernet speed is almost 1 Gbps UL/DL, but the OneDrive client tops out at about 2 MBps. The web interface isn’t much better. Google Drive is a lot faster than that, which makes it a good backup service for manual uploading. Anyway, maybe OneDrive will improve over time; yesterday they delivered an update to OneDrive.app, and at least it finally works.</p> +<p>OneDrive also boasts no file status indicators on OS X, which everyone else in the industry has. That’s not a show-stopper though, if you just use it as a backup service.</p> +<hr/> +<p>What about Dropbox? Dropbox is a truly awesome sync-ready service, but it is at the same time pretty expensive compared to others. Also, since I use Dropbox as a sync service, it must be up at all times and constantly indexing, so I’m really cautious with what I put there to avoid unnecessary cycles and startup time.</p> +<hr/> +<p>Everything is broken in one way or another. Sigh. Let's hope that OneDrive improves a lot in the coming months; if it's stable enough and the speed gets some boost, I'll cancel my Google Drive subscription. I am a Google supporter and Microsoft hater, but a service that <em>works</em> is more important than ideology.</p> +</article> +<hr class="content-separator"/> +<footer class="footer"> +<span class="rfooter"> +<a class="rss-icon" href="/rss.xml" target="_blank" title="RSS feed"><!--RSS feed icon--></a><a class="atom-icon" href="/atom.xml" target="_blank" title="Atom feed"><!--Atom feed icon--></a><a class="cc-icon" href="https://creativecommons.org/licenses/by/4.0/" target="_blank" title="Released under the Creative Commons Attribution 4.0 International license."><!--CC icon--></a> +<a href="https://github.com/zmwangx" target="_blank">Zhiming Wang</a> +</span> +</footer> +</body> +</html> |