Child Item

Dual booting with shared DB drive possible?

I am looking in to buying a new laptop and will need to dual boot Windows and Ubuntu. I am planning three SSD's - one for Windows, one for Ubuntu and one as a shared data drive.

Is it possible to set up DB so that both operating systems can sync to the shared data drive? I have done a bit of research on here and I cannot seem to find a definitive answer.

Thanks!

Find more posts tagged with

Desktop

Sync

Windows

Linux

Insightful

Closed - Partially Delivered

Delivered

Accepted answers

Rich

It's very possible, just not supported or recommended.

Install Dropbox and use the Advanced Options to specify the location for your Dropbox folder. Allow it to sync completely. Boot into the other operating system and install Dropbox, again using Advanced Options to specify the same Dropbox folder. Dropbox will index your files when the installation is complete, but shouldn't need to sync anything unless there have been changes (though it may appear to be syncing, just let it work).

It is extremely important that you DO NOT USE SELECTIVE SYNC from either operating system when running in this configuration. If you do, you WILL lose files.

I would also suggest never booting into the other operating system until you're certain that the current one is fully synced. Also, as always, keep your own backups of your data.

All comments

Jane

Hey @David C.118,

I'd be glad to send over some relevant information.

Please be aware that in order for for Dropbox to work seamlessly, we recommend that only one user account accesses a given Dropbox folder, and that this folder is located on the main drive of your computer or on a drive that is physically connected to the computer. To my mind, it would be better to avoid creating a link to the Dropbox folder, since this may create unexpected behavior and, in some cases, result in file loss.

Please reference this resource to see more details about it.

I hope this helps you clarify! Please let me know if there's anything else I could do to help.

Thanks!

David C.118

I am not really wanting to run DB on a server. I want to dual boot a single machine which will have both Windows and Ubuntu on it. It will have Windows installed on one drive, Ubuntu on another and a third drive will be a data drive that can be seen by both operating systems that I plan to put my DB folder. All drives will be installed on one computer and the only user account accessing that drive will be me.

Rich

It's very possible, just not supported or recommended.

It is extremely important that you DO NOT USE SELECTIVE SYNC from either operating system when running in this configuration. If you do, you WILL lose files.

I would also suggest never booting into the other operating system until you're certain that the current one is fully synced. Also, as always, keep your own backups of your data.

catoir

I was wondering if and how I could suggest DB to implement dual boot as an actual polished feature for those applicable.

It is redundant, and in cases with large DBs, quite wasteful to contain all the same files on one computer 2x. Please, Please and thankyou!

Rich

You can request it in the feature requests section of the forums.

travsformation

This doesn't solve the problem. Once dropbox is installed on one of the OS's, and the Dropbox folder is moved to the shared partition, the Dropbox application on the other OS won't allow you to use that same folder as your Dropbox directory: it issues a "This folder already contains a Dropbox directory" error and can't change the default location." This happens regardless of whether you install Dropbox on one OS first, or on the other.

It would be extremely useful, both for space-saving, and convenience. Is there a way around this?

Rich

@travsformation wrote:
... the Dropbox application on the other OS won't allow you to use that same folder as your Dropbox directory: it issues a "This folder already contains a Dropbox directory" error and can't change the default location."

When that happens, rename the Dropbox folder to Dropbox2 or similar. Reinstall Dropbox and select the location that you want for the Dropbox folder, just like you did on the first OS, and let the installation create a new Dropbox folder. When the installation is finished, Dropbox will immediately start to sync. Exit the Dropbox application to stop syncing. Rename the new Dropbox folder to Dropbox_OLD and rename Dropbox2 to Dropbox. Re-launch Dropbox.

At this point Dropbox will begin indexing all of your files. This process will take a while, especially if you have a lot of data to go through. During this time it may say that files are uploading or downloading, but it's only transferring comparison data and any changes that it find. Be patient and LET IT WORK.

And because it's worth repeating...

It is extremely important that you DO NOT USE SELECTIVE SYNC from either operating system when running in this configuration. If you do, you WILL lose files.

travsformation

I can't believe I didn't think of that! Great workaround, thanks!

chasDSO

I attempted this today, I think this thread is outdated. It looks like the dropbox desktop client for Linux no longer supports ntfs formatted volumes (requires ext4 formatted partition). Thus, it seems now impossible to boot between linux and windows and share dropbox files between them (Windows can not read ext4 formatted partition) - you must have two different dropbox installations - this is from the system requirements page on dropbox:

Linux: Ubuntu 14.04 or higher, Fedora 21 or higher

The Dropbox folder will need to be on an ext4-formatted hard drive or partition
Note: ecryptfs is not supported, but Dropbox will continue to sync with supported file systems that are encrypted via full disk encryption (e.g. LUKS)

So I have a question though. Does anyone know, if I'm booted in Linux, I can see and mount the ntfs drive - so I can open and modify files in the ntfs mounted drive within the dropbox folders for the Windows install. If I modify those files, next time I boot into Windows and the dropbox client runs - will it see the files have changed and synch them?

I'm terribly disappointed that dropbox doesn't support a dual boot scenario and will be investigating alternative storage services now.

BlackBat24

I'm in the same boat as chasDSO. I had been using only one NTFS data drive in my dualboot (win10, ubuntu 18.04 --originally 16.04) for a while now. I'm a PhD student and I run simulations in linux-based clusters, so it's easier to use ubuntu's command line tools, but there's a few things that are better done in windows. DB was one of my backup solutions, and my way of syncing my work (ubuntu), home (dual-boot) and laptop (ubuntu) computers.

I've tried ext2fsd on windows, and while I can read my drive, windows refuses to give me write permissions on an "insecure file system".

Short of duplicating my 1TB DB folder, I see no good solution to this.

David C.118

I had it working seamlesly, however, DB no longer supports NTFS under Linux and so this no longer works.

paloi

I feel the same pain. I have 170 Gb in my Dropbox, therefore I am a paying user.

Counting the Dropbox folder plus the .cache folder plus the DBs ..., goes beyond 200 Gb at my hard disk ...

It looks awkward and wasteful to have 200Gb in a windows partition and again another 200Gb in the Linux partition.

It is rather unaffordable, if you mostly work with laptops, and you expect to have fast SSD drives, as basically a 512 GB SSD which is not cheap will not be enough and then I will need a 1TB SSD drive which is quite expensive.

This thread started with someone trying to eliminate the duplication of the DB, and has evolved into confirming duplication of both, DB and files.

For me, this blow up the competitive advantage that Dropbox has over Google Drive and OneDrive, as until now they were performing quite poorly on Linux (to be gentle, because they do not have Linux client), ... so now this places Dropbox to some short of similar side, where it is only able to work in one of the two OS of my Dual boot laptops.

I can understand the complexity of this, and accept that the indexing is done every-time we switch of OS, and that in the worst case scenario the DB is duplicated ... but having several hundreds of GBs duplicated is not an option for me and most of the dual boot Dropbox clients ...

TripleS

I'm using window 10 and ubuntu 18. I tried to use the same folder for windows and ubuntu however dropbox says:

"To sync your dropbox move your drobox folder to partition with a compariable file system,.. Drop box is compariable with ext4"

Since this thread is outdated, are there any updates?

TripleS

@Здравко - thank you. btw - who wrote this script? have you tested it?

Здравко

The script part is entirely mine and C-code is derived from number other publications.

Ooo.. I didn't see the question for test! Yes, I currently use it. :slight_smile:

Здравко

@TripleS, Sorry, my last publication was one of my drafts. For sure it will not work. It was debug version (some syntax error was still there, missing punctuation). After install I didn't use it for long time (multiple versions was on same place). The next is the last actual version:

#!/bin/bash
##############################################################################
#                    Workaround for Dropbox daemon
#                    -----------------------------
# Verified on Dropbox v73.4.118
# Just make it executable (if need, using
#   $ chmod a+x fix_dropbox
# ) and run it.
# Author: Здравко
#   www.dropboxforum.com/t5/user/viewprofilepage/user-id/422790
##############################################################################

# Figure out the target places.
USR_HOME=`realpath ~`
USR_LOCAL="$USR_HOME/.local"
USR_LOCAL_BIN="$USR_LOCAL/bin"
USR_LOCAL_LIB="$USR_LOCAL/lib"
DRB_REPLACEMENT="$USR_LOCAL_BIN/dropbox"
DRB_FIX_LIB="$USR_LOCAL_LIB/libdropbox_ext4.so"
USR_PROFILE="$USR_HOME/.profile"

##############################################################################
# Precheck and fix up some prerequisites.

# Ensure target directories are on their place.
if [[ ! -d $USR_LOCAL_BIN ]]
then
  echo "The Directory \"$USR_LOCAL_BIN\" doesn't exist, going to create it."
  mkdir -p $USR_LOCAL_BIN
  if [[ $? -ne 0 || ! -d $USR_LOCAL_BIN ]]
  then
    echo "Directory \"$USR_LOCAL_BIN\" creation fail! Exit."
    exit 1
  fi
fi
if [[ ! -d $USR_LOCAL_LIB ]]
then
  echo "The Directory \"$USR_LOCAL_LIB\" doesn't exist, going to create it."
  mkdir -p $USR_LOCAL_LIB
  if [[ $? -ne 0 || ! -d $USR_LOCAL_LIB ]]
  then
    echo "Directory \"$USR_LOCAL_LIB\" creation fail! Exit."
    exit 1
  fi
fi

# Ensure backup for any existing files.
if [[ -e $DRB_REPLACEMENT ]]
then
  if [[ -f $DRB_REPLACEMENT ]]
  then
    echo "\"$DRB_REPLACEMENT\" already exist, going to back it up."
    mv --backup=t -T $DRB_REPLACEMENT "${DRB_REPLACEMENT}.backup"
    if [[ $? -ne 0 || -e $DRB_REPLACEMENT ]]
    then
      echo "Error backing up \"$DRB_REPLACEMENT\" file! Exit."
      exit 1
    fi
  else
    echo "$DRB_REPLACEMENT is not regular file! Exit."
    exit 1
  fi
fi
if [[ -e $DRB_FIX_LIB ]]
then
  if [[ -f $DRB_FIX_LIB ]]
  then
    echo "\"$DRB_FIX_LIB\" already exist, going to back it up."
    mv --backup=t -T $DRB_FIX_LIB "${DRB_FIX_LIB}.backup"
    if [[ $? -ne 0 || -e $DRB_FIX_LIB ]]
    then
      echo "Error backing up \"$DRB_FIX_LIB\" file! Exit."
      exit 1
    fi
  else
    echo "$DRB_FIX_LIB is not regular file! Exit."
    exit 1
  fi
fi

# Ensure writing permissions.
if [[ ! -w $USR_LOCAL_BIN || ! -x $USR_LOCAL_BIN ]]
then
  chmod u+rwx $USR_LOCAL_BIN
  if [[ $? -ne 0 ]]
  then
    echo "The Directory \"$USR_LOCAL_BIN\" is inaccessible! Exit."
    exit 1
  fi
fi
if [[ ! -w $USR_LOCAL_LIB || ! -x $USR_LOCAL_LIB ]]
then
  chmod u+rwx $USR_LOCAL_LIB
  if [[ $? -ne 0 ]]
  then
    echo "The Directory \"$USR_LOCAL_LIB\" is inaccessible! Exit."
    exit 1
  fi
fi

##############################################################################
# Generate actual workaround components.

# Fixer - source and building.
gcc -shared -fPIC -ldl -xc -o $DRB_FIX_LIB - << EndOfSrc
// Functions replacements
#define _GNU_SOURCE

#include <stdlib.h>
#include <sys/vfs.h>
#include <linux/magic.h>
#include <dlfcn.h>
#include <sys/statvfs.h>
#include <stdarg.h>

static int (*orig_statfs)(const char *path, struct statfs *buf) = NULL;
static int (*orig_statfs64)(const char *path, struct statfs64 *buf) = NULL;
static int (*orig_open64)(const char *pathname, int flags, ...) = NULL;

int statfs(const char *path, struct statfs *buf) {
  if (orig_statfs == NULL) {
    orig_statfs = dlsym(RTLD_NEXT, "statfs");
  }
  register int retval = orig_statfs(path, buf);
  if (retval == 0) {
    buf->f_type = EXT4_SUPER_MAGIC;
  }
  return retval;
}

int statfs64(const char *path, struct statfs64 *buf) {
  if (orig_statfs64 == NULL) {
    orig_statfs64 = dlsym(RTLD_NEXT, "statfs64");
  }
  register int retval = orig_statfs64(path, buf);
  if (retval == 0) {
    buf->f_type = EXT4_SUPER_MAGIC;
  }
  return retval;
}

int open64(const char *pathname, int flags, ...) {
  if (orig_open64 == NULL) {
    orig_open64 = dlsym(RTLD_NEXT, "open64");
  }
  register const char *p0 = "/proc/filesystems", *p1 = pathname;
  while(*p0 && *p1 && *p0 == *p1) ++p0, ++p1;
  if (*p0 == '\0' && *p1 == '\0') {
    return -1;
  }
  va_list arg;
  va_start(arg, flags);
  mode_t mode = va_arg (arg, int);
  va_end(arg);
  return orig_open64(pathname, flags, mode);
}
EndOfSrc
if [[ $? -ne 0 ]]
then
  echo "Error building \"$DRB_FIX_LIB\"! Exit."
  exit 2
fi
echo "\"$DRB_FIX_LIB\" - build and ready."

# Wrapper generating.
cat > $DRB_REPLACEMENT << WrapperHead
#!/bin/bash
if [ \$1 == "start" ]
then
  sleep 1
  patchpath=\`which \$0\`
  if echo \$(for i in \`ps -C dropbox -o pid\`
            do ls -l /proc/\$i/exe 2>/dev/null | grep -v \$patchpath
            done) | grep dropbox > /dev/null
  then
    timeout=300
    # Make sure there isn't any concurrent start operation in progress.
    /usr/bin/dropbox running
    while [[ \$? -eq 0 && \$timeout -ne 0 ]]
    do
      sleep 1
      ((--timeout))
      if echo \$(for i in \`ps -C dropbox -o pid\`
                do ls -l /proc/\$i/exe 2>/dev/null | grep -v \$patchpath
                done) | grep dropbox > /dev/null
      then
        /usr/bin/dropbox running
      fi
    done
    # If there is running application instance, force its stop.
    /usr/bin/dropbox running
    while [[ \$? -ne 0 && \$timeout -ne 0 ]]
    do
      /usr/bin/dropbox stop
      sleep 1
      ((--timeout))
      /usr/bin/dropbox running
    done
    # If something goes wrong...
    if [[ \$timeout -eq 0 ]]
    then
      # ...notify somehow about.
      title="Problem launching Dropbox"
      mainmsg="Possible existing application instance dead"
      submsg="Check that, clear and try start again"
      if which notify-send > /dev/null
      then notify-send --icon=dropbox "\$title" "<b>\$mainmsg\!</b>\n\$submsg."
      elif which zenity > /dev/null
      then zenity --error --title="\$title" --timeout=10 --width=380 \\
        --text="<span size=\"xx-large\"><b>\$mainmsg\!</b>\n\$submsg.</span>" \\
        2> /dev/null
      else echo "  \$title!"
        echo "\$mainmsg."
        echo "\$submsg."
      fi
      exit 1
    fi
  fi
fi
WrapperHead
declare -p | grep "declare -x LD_PRELOAD" > /dev/null
if [[ $? -ne 0 ]]
then
  echo "export LD_PRELOAD=$DRB_FIX_LIB" >> $DRB_REPLACEMENT
else
  echo "LD_PRELOAD=$DRB_FIX_LIB:\$LD_PRELOAD" >> $DRB_REPLACEMENT
fi
echo "/usr/bin/dropbox \$@" >> $DRB_REPLACEMENT
chmod a+x $DRB_REPLACEMENT
echo "\"$DRB_REPLACEMENT\" - generated."

# Environment check and fixup (if need).
echo ""
echo ""
(
IFS=:
for a in $PATH
do
  if [[ "$a" == "$USR_LOCAL_BIN" ]]
  then
    exit 0
  elif [[ "$a" == "/usr/bin" ]]
  then
    break
  fi
done
exit 1
)
if [[ $? -ne 0 ]]
then
  echo "" >> $USR_PROFILE
  echo "" >> $USR_PROFILE
  echo "# Add $USR_LOCAL_BIN to \$PATH environment variable." >> $USR_PROFILE
  echo "# This addition is dedicated for Dropbox Workaround." >> $USR_PROFILE
  echo "# Remove theses lines when they are no more needed." >> $USR_PROFILE
  echo "PATH=\"$USR_LOCAL_BIN:\$PATH\"" >> $USR_PROFILE
  echo "" >> $USR_PROFILE
  echo "Your Dropbox is almost patched. You have to logout and login"
  echo " (or on Your opinion - restart), so all changes to take effect."
  echo "After Your next account login:"
fi
echo "Your Dropbox is already patched. Just start it from desktop GUI or type:"
echo "\$ dropbox start"
echo "in console."

paloi

@Здравко Thanks for your posting, it looks like a new hope after so many months.

Could you please confirm what the script does?

Not only the workarround to have the Dropbox only once over the NTFS locations, but also a single DB which avoids reindexing every time one boots with the other OS, plus support for selective sync?

Здравко

Hi @paloi, Yes, I reinstall it just to be sure (after detecting that the last publication wasn't the recent). Exact function is: mask the underlying filesystem, so for Dropbox it looks like Ext4 (doesn't matter what is realy). The change is only how it looks like, there are no any actual changes in real filesystem.

Здравко

I don't use selective sync, so this is not tested.

chasDSO

'..There is no common format that is supported on each operating system....'

That post doesn't make sense. You don't need compat formats on the drive system. Dropbox should just be copying down folders and files to the file system irrespective of what format. Any of those will support the same files - for instance, you can dload .docx or linux text files just fine to any format - disk format is irrelevent.

There is no technology reason why Dropbox decided to end support for this option - they supported it in the past I believe but functionality was removed.

Здравко

Hi @chasDSO,

Yes, You are absolutely right! I don't know (and not just me) why Dropbox set this limitation. My work is just workaround the limitation. :slight_smile:

Rich

@chasDSO wrote:
'..There is no common format that is supported on each operating system....'

That post doesn't make sense.

In terms of Dropbox, yes, it does. Dropbox does not support NTFS for Linux, anything other than NTFS for Windows, etc. Are there workarounds? Yes, apparently, but that doesn't make my comment invalid. In reference to Dropbox and how it works, there is no common format that will allow the official Dropbox client to work across mutliple operating systems. I'm not talking hacks or workarounds. I'm not talking about Linux being able to access NTFS. I'm talking naitive Dropbox support of the file system.

Regardless, I removed that last post of mine since Здравко has a workaround.

There is no technology reason why Dropbox decided to end support for this option - they supported it in the past I believe but functionality was removed.

No one ever said there was a technology reason for it. No one is debating that. Dropbox simply doesn't support it anymore. Technically they never officially supported it, but it worked.

Здравко

@Rich wrote:
...
No one ever said there was a technology reason for it. No one is debating that. Dropbox simply doesn't support it anymore. Technically they never officially supported it, but it worked.

Almost, but not exactly! In fact You are right, there wasn't (and is not) any technology. Dropbox (or any other such service) don't need to support this. This is OS responsibility! And, in this context, it's not clear why was this limitation added (not support missing)! Support is not need.

Rich

@Здравко wrote:
Support is not need.

You're confusing support from a technology standpoint (Product A working with Product and support from a business standpoint (Company A saying "No, we don't allow that.").

Dropbox never officially supported Dropbox being used in such a configuration. They didn't design it to work like that, and if a person wasn't careful they could cause damage to their files or possibly lose data (like by using Selective Sync in such a configuration). I'm guessing that's the reason Dropbox no longer supports their product being used in such a way. They could simply be trying to make it more idiot-proof, like they've been trying to do for years.

unknown

I am just trying out your workaround. I hope it works for the computer has been syncronizing for an hour and not yet done. I had 60 GB of data and want to access them from a dual boot Windows-Windows computer. Nevertheless your idea deserved a try. Thanks !

Здравко

anonymous wrote:
... want to access them from a dual boot Windows-Windows computer. ...

Hi anonymous,

Please note that the above script work and is tested on Linux only. Probably, might be usable also on Mac with some adaptations. There is no any chance to be used directly on Windows! Windows API is completely different and only partially compatible with POSIX (the standard functions used in the C code). Also 'bash' script interpreter is usually not available on Windows, if not explicitly installed.

Unfortunately, this solution couldn't be usable for you. But you can get out the idea and port it.

unknown

I was replying to Rich's post dated 04-11-2018 08:40 PM about the issue of Dropbox not allowing dual booting with the SAME operating system, namely Windows. His workaround implying renaming the Dropbox folder to cheat the Dropbox desktop application. It worked for me with only reporting "Conflicting Copies" in some (a couple hundreds) Excel files between the two Windows 7 operating systems. But apparently it is working. Thanks QA

sharky_pi

Similar position to Chas & Blackbat: if I

Install dropbox to an ext4 linux partition,
Boot into windows, access a dropbox-folder file using ext4fsd, edit it, save it,
Boot back into linux

How will dropbox cope/deal with the changed file?

A. Complete reindex (I have ~14gb FWIW)

B. Diff check against logs, finds single file change, indexes, uploads

C. Something else?

Cheers!