-2

I have two Digital Ocean droplets (Ubuntu 14.04 LTS VPS instances):

  • Alice: 40GB disk / 38GB used
  • Bob: 20GB disk / 2GB used

Alice’s storage needs will continue to grow slowly but steadily. Rather than bumping Alice up to a more expensive image, is there an effective way of sharing some of Bob’s disk to Alice? I’m looking to transparently extending the filesystem rather than creating an additional partition if possible. Both droplets are hosted in the Digital Ocean nyc2 datacenter, both use a single ext4 partition, and they seem to have excellent connectivity between them.

3 Answers 3

1

Rather than bumping Alice up to a more expensive image, is there an effective way of sharing some of Bob's disk to Alice?

What you are talking about comes down to being so intricate—NFS mounts, etc…—that ultimately you might be better off growing Alice’s space to a more expensive image.

But part of the problem with the question is what exactly is eating up space? Actual application usage on the server? Files that need to be accessed immediately or archival items? Because you say:

I’m looking to transparently extending the filesystem rather than creating an additional partition if possible.

But honestly doing that transparently is not going to be easy. You need to better define—for us and for you—what’s eating up the space.

Perhaps something like Amazon S3 can help you offload your storage for the application running on the server itself.

But you need to provide more details since simply saying “more storage” does not address the issue.

EDIT: Based on the original poster’s comments this is about Bitcoin related files stored in .bitcoin/. The key thing you need to keep in mind is these are simply files store on a oath. So figure out where your .bitcoin/ directory is located, then see if you can adjust a config to change that path where they are stored. If you can change that path—which I am pretty confident yo can—then perhaps an NFS mount would work. Just setup an NFS mount, move the old block chain stuff to the new space, change the config to point to that new space & restart the process. But honestly you might be doing more work than it’s worth.

3
  • It's a bitcoind node. The blockchain is growing steadily. Specifically: 1.9G .bitcoin/blocks/index 22G .bitcoin/blocks 24K .bitcoin/database 410M .bitcoin/chainstate 22G .bitcoin/
    – Ryan
    May 10, 2014 at 16:05
  • @Ryan Okay, so figure out where your blockchain is located, then see if you can adjust the config to change that path. If you can change that path, then perhaps an NFS mount would work. Just setup an NFS mount, move the old block chain stuff to the new space, change the config to point to that new space & restart the process. But honestly you might be doing more work than is worth it. May 10, 2014 at 16:08
  • 1
    Bob would have less than the size of the blockchain to share, so I'll agree it's probably more work than is worth it.
    – Ryan
    May 10, 2014 at 16:16
0

It depends on what you mean by "sharing", but some approaches

  • NFS/SMB/sshfs: Bob will offer a directory of his file system where both can write/read to.
  • iSCSI: Bob will offer a part of his space as a iSCSI block device. This can be used by Alice at will, e.g. as LVM PV, but not by Bob anymore (except Alice shares it back via NFS/SMB/sshfs).
-1

Yes, there are ways to achieve something like this. But your question seems to indicate you're trying to circumvent the pricing structure of your VPS host. Questions asking about misusing services or equipment are inappropriate, just so you know.

You need to check with the policies of Digital Ocean and see what they allow. Just because you can do something doesn't mean you should do it. That being said, you may be able to use a network filesystem to get access to one instance's storage from another. Of course, that means you'll need to manage the different sized space allocations, but that's part of being an administrator. ;-)

2
  • fdmillion: If the hoster offers free traffic between hosts, he can and must expect that disk space gets shared this way. I can't see any wrongdoing on the part of the customer and would leave a provider immediately if he tries to prevent this.
    – Sven
    May 10, 2014 at 15:55
  • “You need to check with the policies of Digital Ocean and see what they allow.” Most virtual hosts provide an internal IP address as well as an external & generally charge for traffic on the external, but allow the internal with baked-in traffic caps. Meaning an NFS mount might be possible, but it still might be more of a hassle than it’s worth. No wrongdoing. May 10, 2014 at 16:06

Not the answer you're looking for? Browse other questions tagged or ask your own question.