How can I get permanent blob container mount with BlobFuse2 in Linux VM ?

Question

How can I get permanent blob container mount with BlobFuse2 in Linux VM ?

Galgani, Stefano 205

Hi all,

I implemented the mount container inside Linux VM (RedHat 8.6) through blobfuse2 lib.

As I described the steps at the link . I put the necessary scripts and config files in a folder created by me (etc/blobfuse) inside the Linux VM.

Once performed the scripts the mount container worked fine, but after a little days , I was not able to find the mount inside Linux VM and I knew that nobody has had interaction with the Linux VM.

I'm assuming the VM lost the mount due to restart.

How can I get permanent blob container mount with BlobFuse2 lib in Linux VM ?

Could you provide a right solution to implement it ?

Thanks

Galgani, Stefano 205 Reputation points

2023-08-25T13:31:46.63+00:00

@Ramya Harinarthini_MSFT
I replayed to your points:

R1) I have installed blobFuse2 lib inside Linux VM (2.0.5 version)

R2) I have two config files linked to different storage accounts with only mount.sh file.
In nutshell I have a single mount.sh file to perform the mount commands for both containers.
Probably I will have to split mount.sh in two different files to let me use the command string that you
told me at the point 3 ( for editing fstab file)

Let me try and I will update the post

Galgani, Stefano 205

Hi @Ramya Harinarthini_MSFT
I have used your second option and it working fine, but I had to add some details:

I had to add the followed properties to the config mount file because at every restart of the vm the mount was lost.

file_cache:
path: /tmp/blobfuse2tmp
timeout-sec: 120

so the final config mount file is the followed:

allow-other: true

logging:
  type: syslog
  level: log_debug

components:
  - libfuse
  - stream
  - attr_cache
  - azstorage

libfuse:
  attribute-expiration-sec: 120
  entry-expiration-sec: 120
  negative-entry-expiration-sec: 240

stream:
  block-size-mb: 8
  blocks-per-file: 3
  cache-size-mb: 1024

attr_cache:
  timeout-sec: 7200

azstorage:
  type: block
  account-name: testS06d
  endpoint: https://testS06d.blob.core.windows.net
  mode: msi
  container: test-container

file_cache:
path: /tmp/blobfuse2tmp
timeout-sec: 120

Your second option that you told me, but with the different syntax appended on fstab file

blobfuse2 /mnt/test-container fuse3 defaults,_netdev,--config-file=<path config file>/configBlobFuse.yaml,allow_other 0 0

Thanks

Accepted answer

0 additional answers

Your answer

Galgani, Stefano 205 Reputation points

2023-08-25T13:31:46.63+00:00

@Ramya Harinarthini_MSFT
I replayed to your points:

R1) I have installed blobFuse2 lib inside Linux VM (2.0.5 version)

R2) I have two config files linked to different storage accounts with only mount.sh file.
In nutshell I have a single mount.sh file to perform the mount commands for both containers.
Probably I will have to split mount.sh in two different files to let me use the command string that you
told me at the point 3 ( for editing fstab file)

Let me try and I will update the post
Galgani, Stefano 205 Reputation points

2023-08-28T14:33:06.67+00:00

Hi @Ramya Harinarthini_MSFT
I have used your second option and it working fine, but I had to add some details:

I had to add the followed properties to the config mount file because at every restart of the vm the mount was lost.

file_cache: path: /tmp/blobfuse2tmp timeout-sec: 120

so the final config mount file is the followed:

allow-other: true logging: type: syslog level: log_debug components: - libfuse - stream - attr_cache - azstorage libfuse: attribute-expiration-sec: 120 entry-expiration-sec: 120 negative-entry-expiration-sec: 240 stream: block-size-mb: 8 blocks-per-file: 3 cache-size-mb: 1024 attr_cache: timeout-sec: 7200 azstorage: type: block account-name: testS06d endpoint: https://testS06d.blob.core.windows.net mode: msi container: test-container file_cache: path: /tmp/blobfuse2tmp timeout-sec: 120

Your second option that you told me, but with the different syntax appended on fstab file

blobfuse2 /mnt/test-container fuse3 defaults,_netdev,--config-file=<path config file>/configBlobFuse.yaml,allow_other 0 0

Thanks

Answer 1

Ramya Harinarthini_MSFT 5,366 Microsoft Employee Moderator

Galgani, Stefano

Just wanted to check with you if you have followed the below steps to persist mount with BlobFuse2 lib mentioned in the article: https://github.com/Azure/azure-storage-fuse/wiki/Blobfuse2-Installation#persisting-mount

Make sure the fuse package is installed (e.g., yum install fuse3 / apt-get install fuse3)
Update config.yaml file with your preferred configuration.
Edit /etc/fstab with the blobfuse script.

Add the following line to use mount.sh:

/<path_to_blobfuse2_mount.sh_file>/mount.sh   </path/to/desired/mountpoint>     fuse    defaults,_netdev 0 0

OR

Add the following line to run without mount.sh

blobfuse2 /home/azureuser/mntblobfuse fuse defaults,_netdev,--config-file=/home/azureuser/config.yaml,allow_other 0 0

Galgani, Stefano 205

Hi @Ramya Harinarthini_MSFT
I have used your second option and it working fine, but I had to add some details:

I had to add the followed properties to the config mount file because at every restart of the vm the mount was lost.

file_cache:
path: /tmp/blobfuse2tmp
timeout-sec: 120

so the final config mount file is the followed:

allow-other: true

logging:
  type: syslog
  level: log_debug

components:
  - libfuse
  - stream
  - attr_cache
  - azstorage

libfuse:
  attribute-expiration-sec: 120
  entry-expiration-sec: 120
  negative-entry-expiration-sec: 240

stream:
  block-size-mb: 8
  blocks-per-file: 3
  cache-size-mb: 1024

attr_cache:
  timeout-sec: 7200

azstorage:
  type: block
  account-name: testS06d
  endpoint: https://testS06d.blob.core.windows.net
  mode: msi
  container: test-container

file_cache:
path: /tmp/blobfuse2tmp
timeout-sec: 120

Your second option that you told me, but with the different syntax appended on fstab file

blobfuse2 /mnt/test-container fuse3 defaults,_netdev,--config-file=<path config file>/configBlobFuse.yaml,allow_other 0 0

Thanks

Share via

How can I get permanent blob container mount with BlobFuse2 in Linux VM ?

0 additional answers

Your answer