Closed murphycj closed 3 years ago
I should also add that when I initially setup myvolume
I manually spun up a t2.micro instance and attached the volume to it and ran the following commands:
drive='xvdf'
sudo mkdir /data
sudo mkfs -t xfs /dev/$drive
sudo mount /dev/$drive /data
sudo chown ec2-user:ec2-user /data
I then detached the volume and proceeded to try to use it with spotty. I mention all this in case any of the above commands somehow conflict with spotty. I am not very familiar with disk formatting and stuff.
Ok, so I tried out formatting a new volume with a different file system time (e.g. sudo mkfs -t ext4 /dev/$drive
). Trying out that new volume works with spotty. So the issue is spotty assumes the volume has a certain filesystem type.
Thanks so much for creating spotty, so far it seems like a great tool! However, I had an issue mounting a volume (named
myvolume
) to a new instance. Below is the error I get:However, it had no issue mounting another volume that it created on the fly. Here is the relevant portion of my
spotty.yaml
so you know what I mean:I am able use the
spotty sh -H
command and see both volumes are mounted though.Also, please note that
myvolume
volume is that it is of typegp3
, and I saw in the documentation it is not one of the supported EBS types. So maybe that is the issue? If so, any plans on supportinggp3
volume type?Thanks!