Reason being, we have nearly 1TB of images as we use fog A LOT! So to become more stable, we built a new server, created a raid5 array for all the images to be saved on. The problem appears to be linking all this so that fog can read/write images from it’s /images storage node which just happens to be a raid5 array on the main server. etc/fstab: images /images vboxsf noauto 0 0Īll of the image subfolders from within /storage/images have mounted properly within the host /images.įog gui disk information shows the free and used space to be the same as the raid array. ![]() Called “images” and does not automount so solve previous problems. –I have set up a shared folder from within the virtualbox settings which shares /storage/images with the host. The server is running virtual box of which the host is ubuntu desktop. This is a copy of all of my fog images backed up from my old fog server, once again, I can at the moment access/delete all files within. This works perfectly fine, I can copy/paste files to and from this. ![]() Running a raid5 array - mounted at /storage. Ubuntu server (booting from a separate SSD): Bit of an interesting one that I’m trying to solve however there’s so many variables it’s a tad confusing so the set up is this:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |