cloud engineer
s3fs allows Linux to mount S3 buckets as a file system.
Install s3fs.
sudo apt install s3fs |
sudo apt install s3fs
Setup credentials.
echo ACCESS_KEY_ID:SECRET_ACCESS_KEY > ${HOME}/.passwd-s3fs chmod 600 ${HOME}/.passwd-s3fs |
echo ACCESS_KEY_ID:SECRET_ACCESS_KEY > ${HOME}/.passwd-s3fs chmod 600 ${HOME}/.passwd-s3fs
Mount it.
s3fs bucketname /mountpoint -o passwd_file=${HOME}/.passwd-s3fs |
s3fs bucketname /mountpoint -o passwd_file=${HOME}/.passwd-s3fs
Mount it automatically.
bucketname /mountpoint fuse.s3fs _netdev,allow_other,passwd_file=/home/user/.passwd-s3fs,rw,uid=1000,gid=1000 0 0 |
bucketname /mountpoint fuse.s3fs _netdev,allow_other,passwd_file=/home/user/.passwd-s3fs,rw,uid=1000,gid=1000 0 0
While trying to recover a directory from backup, I ran into an issue with duplicate uuids when trying to mount a recovered volume. The problem was the recovered volume had the same uuid as boot.
Here’s the original mount command I ran, but I was getting a wrong fs type error.
mkdir mount -t xfs /dev/nvme3n1p2 /recover mount: wrong fs type, bad option, bad superblock on /dev/nvme3n1p2, missing codepage or helper program, or other error |
mkdir mount -t xfs /dev/nvme3n1p2 /recover mount: wrong fs type, bad option, bad superblock on /dev/nvme3n1p2, missing codepage or helper program, or other error
It turned out to be a duplicated uuid. To get around this problem, I ran -o nouuid.
mount -t xfs -o nouuid /dev/nvme3n1p2 /recover |
mount -t xfs -o nouuid /dev/nvme3n1p2 /recover
Once the files were recovered, I unmounted volume and detached it from the instance.
Here’s how to format a USB drive on Linux.
Plug in the USB drive to see mount point.
# scan for all drives df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/sdc1 fuseblk 30G 66M 30G 1% /media/ulysses/451B99AF225B48EC |
# scan for all drives df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/sdc1 fuseblk 30G 66M 30G 1% /media/ulysses/451B99AF225B48EC
Unmount USB drive.
umount /dev/sdc1 |
umount /dev/sdc1
Choose a file system type and run the appropriate format command.
# nfts format mkfs.ntfs /dev/sdc1 # vfat format mkfs.vfat /dev/sdc1 # ext4 format mkfs.ext4 /dev/sdc1 |
# nfts format mkfs.ntfs /dev/sdc1 # vfat format mkfs.vfat /dev/sdc1 # ext4 format mkfs.ext4 /dev/sdc1
Here’s how to setup a XFS volume.
file -s /dev/nvme2n1 mkfs -t xfs /dev/nvme2n1 |
file -s /dev/nvme2n1 mkfs -t xfs /dev/nvme2n1
Mount to /data.
mkdir /data mount /dev/nvme2n1 /data |
mkdir /data mount /dev/nvme2n1 /data
Add to /etc/fstab.
vim /etc/fstab # # UUID=xxxxxxxxxxxxxxxxxxxxxx /data xfs defaults 0 0 |
vim /etc/fstab # # UUID=xxxxxxxxxxxxxxxxxxxxxx /data xfs defaults 0 0
To automatically mount a EFS volume after each reboot, you’ll need to add the following format to /etc/fstab.
You can use the DNS name given by AWS.
fs-12345678:/ /mnt/efs efs defaults,_netdev 0 0 |
fs-12345678:/ /mnt/efs efs defaults,_netdev 0 0
Or the IP address.
10.0.0.22:/ /mnt/efs efs defaults,_netdev 0 0 |
10.0.0.22:/ /mnt/efs efs defaults,_netdev 0 0
Mount all with fake and verbose.
mount -fav |
mount -fav