Storj Node expansion

[Alexey]

@BrightSilence

Yeah, but you need to already be using it right? Or is there a way to convert a live partition to LVM?

Depends. See

@Alexey

I installed the LVM and successfully converted GPT partition to LVM (this is a very precise task, you can easily lost everything , see Convert an existing Linux file system to LVM – Pascal Roeleven). So create your LVM partition right away, converting will not be an easy task later.

@BrightSilence

Maybe lowering the node capacity and just doing a dumb copy of the globe folder while running should be offered as an alternative in the docs? @Alexey how do you feel about that? Or is that a bad idea to suggest to node operators?

It’s not bad, but requires to be careful. With rsync the worst case is corrupted databases, if the operator would forgot to do last rsync with --delete option.
In the suggested method there is a great chance to lost data, especially on Windows, where you cannot copy an opened file with usual Explorer or even copy command.
So, you need to use rsync/robocopy anyway at the end. But since the copy command changes the modification date, rsync will likely copy it over again, so you have nothing to save in time.

Maybe we can write a guide to use the suggested method extended with special options in the cp command to preserve a modification time and do the last sync with rsync --delete.
I have a feeling, that resulted time would not change, because most of it rsync seems to spend on calculating a difference, not on copy. This is especially true for NTFS under Linux (it’s known as incredibly slow).