Unable to Mount blobfuse on redhat server Error : 403

Sumarigo-MSFT 47,506 Reputation points Microsoft Employee Moderator
2021-10-27T15:25:52.213+00:00

We are facing issue in mounting blobfuse on redhat server below is the error output, from same storage we are able to mount on other 3 container with same credentials
Error code - HTTP 403;
Storage server request ID - 33da8899-501e-0033466-7079-8b7487000033400;
Blob container - <Conatiner name>;
Blob path - ;

Unable to start blobfuse. Failed to connect to the storage container. There might be something wrong about the storage config, please double check the storage account name, account key/sas token/OAuth access token and container name. error = 403


Note: This question is being posted as part of an internal effort at Microsoft to share emerging content with the community. A Microsoft employee will be following up with an answer shortly. If you have feedback regarding this issue, we encourage the community to start a discussion in the comments.

Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Sumarigo-MSFT 47,506 Reputation points Microsoft Employee Moderator
    2021-10-27T15:49:26.407+00:00

    Cause: The following error is observed when mounting a storage container as a BlobFuse mount:
    As have observed the impacted Storage Account ‘<Account name>’ has its Firewall enabled and currently, does not allow the source subnet to connect.

    Resolution : If the identified source subnet is confirmed to be correct, please allow this subnet through the Azure Storage Firewall and retry the mounting operation..

    Note: Blobfuse stores all open file contents in the temporary path. Make sure to have enough space to accommodate all open files.

    Once you have installed blobfuse, configure your account credentials either in the template provided in blobfuse folder (connection.cfg), or in the environment variables. For brevity, let's use the following environment variables for authentication using account name and key:

    Additional information: Here are the steps to mount on Redhat Linux (This is temp mount, not persisting)

    subscription-manager register --username <> --password <password removed> --auto-attach   
    sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm   
    sudo yum install blobfuse fuse   
       
    sudo mkdir /mnt/blobfusetmp   
    sudo chown <youruser> /mnt/blobfusetmp  
      
    sudo mount -t tmpfs -o size=1g tmpfs /mnt/blobfusetmp   
       
    export AZURE_STORAGE_ACCOUNT=xwfileping    
    export AZURE_STORAGE_ACCESS_KEY=<Key removed>   
       
    blobfuse /blobfuse --tmp-path=/mnt/blobfusetmp -o attr_timeout=240 -o entry_timeout=240 -o negative_timeout=120 -o allow_other --container-name=transfer --log-level=LOG_DEBUG --file-cache-timeout-in-seconds=120    
    
     
    

    To mount a persisting folder, you may download the https://github.com/Azure/azure-storage-fuse/blob/master/mount.sh, and use credentials in a file method to mount the folder.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.