Closed kumaaaah closed 1 year ago
Hi. Our team is experiencing the same issue with blobfuse2 on AKS 1.24.10. We have enabled managed blob-csi driver and its version is v1.19.2. The following error is produced during unmount:
mount_helper_common.go:150] Warning: deleting path "/var/lib/kubelet/pods/ab292926-4f67-43cb-a848-7ed8feeaa482/volumes/kubernetes.io~csi/bundle-reports-volume/mount" utils.go:80] GRPC error: rpc error: code = Internal desc = failed to unmount target "/var/lib/kubelet/pods/ab292926-4f67-43cb-a848-7ed8feeaa482/volumes/kubernetes.io~csi/bundle-reports-volume/mount": remove /var/lib/kubelet/pods/ab292926-4f67-43cb-a848-7ed8feeaa482/volumes/kubernetes.io~csi/bundle-reports-volume/mount: device or resource busy utils.go:75] GRPC call: /csi.v1.Node/NodeUnpublishVolume
From the discussion above I understood that the fix landed in v1.19.2 and deployed to managed blob-csi drivers with the 0319 release (which is deployed to our location
West Europe
). Is it expected behaviour?
@kvet this could be different issue, during the unmount, you application would receive SIGTERM signal, and then application should stop writing data to blobfuse volume first, and then unmount would succeed. You could set preStop hook to terminiate the application when it receives SIGTERM signal from kubernetes
@kvet to make sure whether your blobfuse2 mount is affected since the bug is in v1.19.1, and if your blobfuse2 mount was using v1.19.1 (happened before v1.19.2 rollout), then it may have issue. I think you could schedule your pods with blobfuse2 volume to new node or node without any blobfuse2 volume mount, that could make sure the original blobfuse2 mount is always using v1.19.2, hope that answers your question.
@andyzhangx I don't think it's related to the writing as I am mounting the PV with read-only access... But even in the case of an ongoing write to the volume, it still makes sense that the driver manages to properly handle it. With blobfuse1 we are not experiencing similar issues.
About what is exactly happening. On a fresh node, the driver allows mounting the volume once. I can list connected drives with df -h
during that first mount and get the desired blobfuse2
mount. On subsequent mounts, I no longer see the mounted drive. But I can see with the mount
command: /dev/sda1 on /mnt/bundle-reports type ext4 (ro,relatime,discard)
.
@kvet the blobfuse2 mount took 18s to mount complete, not sure why it took so long time, is your agent node very busy? that means the original sleep 2s
workaround in v1.19.2
may not work
I0413 10:16:36.337000 7369 nodeserver.go:158] calling BlobfuseProxy: MountAzureBlob function
I0413 10:16:54.750362 7369 nodeserver.go:401] volume(strippedaccount#bundle-reports#handle1) mount on "/var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/244a63d20804f80d4ced5a3b49541134bb20325e65864c3b9242abc52ff172d9/globalmount" succeeded
We have published a new v1.19.3 release that could fix this issue ultimately, pls share me with your aks cluster fqdn via mail (you could find my mail address from github), and I could upgrade the version to v1.19.3 from backend directly.
@andyzhangx the cluster received the update. Thank you!
I run into a different issue... The driver fails to mount a volume. Even on the first mount. (I run it on a node that no longer had a mounted blob volume and received the update as well as on a node that didn't have a mounted volume before.) The results are the same.
The node itself is not busy. There are a number of running pods, but the resource usage is under 15% for CPU and 30% for RAM.
@andyzhangx the cluster received the update. Thank you!
I run into a different issue... The driver fails to mount a volume. Even on the first mount. (I run it on a node that no longer had a mounted blob volume and received the update as well as on a node that didn't have a mounted volume before.) The results are the same.
The node itself is not busy. There are a number of running pods, but the resource usage is under 15% for CPU and 30% for RAM.
Logs
I0417 08:08:25.143516 3245281 main.go:117] set up prometheus server on [::]:29635 I0417 08:08:25.144094 3245281 blob.go:235] DRIVER INFORMATION: ------------------- Build Date: "2023-04-15T07:29:33Z" Compiler: gc Driver Name: blob.csi.azure.com Driver Version: v1.19.3 Git Commit: 60c085f6efddc41cca32eabcae8e5e5eed4b905e Go Version: go1.20.3 Platform: linux/amd64 Streaming logs below: I0417 08:08:25.144241 3245281 blob.go:238] driver userAgent: blob.csi.azure.com/v1.19.3 AKS I0417 08:08:25.144637 3245281 azure.go:73] set QPS(25.000000) and QPS Burst(50) for driver kubeClient I0417 08:08:25.144916 3245281 azure.go:87] reading cloud config from secret kube-system/azure-cloud-provider I0417 08:08:30.196177 3245281 azure.go:94] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found I0417 08:08:30.196198 3245281 azure.go:99] could not read cloud config from secret kube-system/azure-cloud-provider I0417 08:08:30.196204 3245281 azure.go:102] AZURE_CREDENTIAL_FILE env var set as /etc/kubernetes/azure.json I0417 08:08:30.196231 3245281 azure.go:113] read cloud config from file: /etc/kubernetes/azure.json successfully I0417 08:08:30.196851 3245281 azure_auth.go:245] Using AzurePublicCloud environment I0417 08:08:30.196872 3245281 azure_auth.go:96] azure: using managed identity extension to retrieve access token I0417 08:08:30.196881 3245281 azure_auth.go:102] azure: using User Assigned MSI ID to retrieve access token I0417 08:08:30.196905 3245281 azure_auth.go:113] azure: User Assigned MSI ID is client ID I0417 08:08:30.196944 3245281 azure.go:775] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000 I0417 08:08:30.196984 3245281 azure_interfaceclient.go:74] Azure InterfacesClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.196993 3245281 azure_interfaceclient.go:77] Azure InterfacesClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197006 3245281 azure_vmsizeclient.go:68] Azure VirtualMachineSizesClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197009 3245281 azure_vmsizeclient.go:71] Azure VirtualMachineSizesClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197022 3245281 azure_snapshotclient.go:70] Azure SnapshotClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197025 3245281 azure_snapshotclient.go:73] Azure SnapshotClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197030 3245281 azure_storageaccountclient.go:70] Azure StorageAccountClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197032 3245281 azure_storageaccountclient.go:73] Azure StorageAccountClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197041 3245281 azure_diskclient.go:68] Azure DisksClient using API version: 2022-03-02 I0417 08:08:30.197050 3245281 azure_diskclient.go:73] Azure DisksClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197052 3245281 azure_diskclient.go:76] Azure DisksClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197058 3245281 azure_vmclient.go:70] Azure VirtualMachine client (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197063 3245281 azure_vmclient.go:73] Azure VirtualMachine client (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197079 3245281 azure_vmssclient.go:70] Azure VirtualMachineScaleSetClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197084 3245281 azure_vmssclient.go:73] Azure VirtualMachineScaleSetClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197092 3245281 azure_vmssvmclient.go:75] Azure vmssVM client (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197100 3245281 azure_vmssvmclient.go:78] Azure vmssVM client (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197112 3245281 azure_routeclient.go:69] Azure RoutesClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197116 3245281 azure_routeclient.go:72] Azure RoutesClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197124 3245281 azure_subnetclient.go:70] Azure SubnetsClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197128 3245281 azure_subnetclient.go:73] Azure SubnetsClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197136 3245281 azure_routetableclient.go:69] Azure RouteTablesClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197141 3245281 azure_routetableclient.go:72] Azure RouteTablesClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197148 3245281 azure_loadbalancerclient.go:70] Azure LoadBalancersClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197156 3245281 azure_loadbalancerclient.go:73] Azure LoadBalancersClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197163 3245281 azure_securitygroupclient.go:70] Azure SecurityGroupsClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197183 3245281 azure_securitygroupclient.go:73] Azure SecurityGroupsClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197192 3245281 azure_publicipclient.go:74] Azure PublicIPAddressesClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197196 3245281 azure_publicipclient.go:77] Azure PublicIPAddressesClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197207 3245281 azure_blobclient.go:67] Azure BlobClient using API version: 2021-09-01 I0417 08:08:30.197216 3245281 azure_vmasclient.go:70] Azure AvailabilitySetsClient (read ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197220 3245281 azure_vmasclient.go:73] Azure AvailabilitySetsClient (write ops) using rate limit config: QPS=10, bucket=100 I0417 08:08:30.197271 3245281 azure.go:1006] attach/detach disk operation rate limit QPS: 6.000000, Bucket: 10 I0417 08:08:30.197287 3245281 azure.go:149] starting node server on node(stripped-node) I0417 08:08:30.197298 3245281 blob.go:243] cloud: AzurePublicCloud, location: westeurope, rg: rg, VnetName: vnet, VnetResourceGroup: vnet-rg, SubnetName: main I0417 08:08:30.199130 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:08:30.199180 3245281 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME I0417 08:08:30.199189 3245281 driver.go:80] Enabling controller service capability: EXPAND_VOLUME I0417 08:08:30.199201 3245281 driver.go:80] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER I0417 08:08:30.199209 3245281 driver.go:99] Enabling volume access mode: SINGLE_NODE_WRITER I0417 08:08:30.199211 3245281 driver.go:99] Enabling volume access mode: SINGLE_NODE_READER_ONLY I0417 08:08:30.199214 3245281 driver.go:99] Enabling volume access mode: SINGLE_NODE_SINGLE_WRITER I0417 08:08:30.199216 3245281 driver.go:99] Enabling volume access mode: SINGLE_NODE_MULTI_WRITER I0417 08:08:30.199218 3245281 driver.go:99] Enabling volume access mode: MULTI_NODE_READER_ONLY I0417 08:08:30.199221 3245281 driver.go:99] Enabling volume access mode: MULTI_NODE_SINGLE_WRITER I0417 08:08:30.199223 3245281 driver.go:99] Enabling volume access mode: MULTI_NODE_MULTI_WRITER I0417 08:08:30.199226 3245281 driver.go:90] Enabling node service capability: STAGE_UNSTAGE_VOLUME I0417 08:08:30.199233 3245281 driver.go:90] Enabling node service capability: SINGLE_NODE_MULTI_WRITER I0417 08:08:30.199337 3245281 server.go:114] Listening for connections on address: &net.UnixAddr{Name:"//csi/csi.sock", Net:"unix"} I0417 08:08:30.711845 3245281 utils.go:75] GRPC call: /csi.v1.Identity/GetPluginInfo I0417 08:08:30.711867 3245281 utils.go:76] GRPC request: {} I0417 08:08:30.713155 3245281 utils.go:82] GRPC response: {"name":"blob.csi.azure.com","vendor_version":"v1.19.3"} I0417 08:08:30.713454 3245281 utils.go:75] GRPC call: /csi.v1.Identity/GetPluginInfo I0417 08:08:30.713465 3245281 utils.go:76] GRPC request: {} I0417 08:08:30.713490 3245281 utils.go:82] GRPC response: {"name":"blob.csi.azure.com","vendor_version":"v1.19.3"} I0417 08:08:31.089158 3245281 utils.go:75] GRPC call: /csi.v1.Node/NodeGetInfo I0417 08:08:31.089172 3245281 utils.go:76] GRPC request: {} I0417 08:08:31.089227 3245281 utils.go:82] GRPC response: {"node_id":"stripped-node"} I0417 08:11:47.085876 3245281 utils.go:75] GRPC call: /csi.v1.Node/NodeStageVolume I0417 08:11:47.085891 3245281 utils.go:76] GRPC request: {"secrets":"***stripped***","staging_target_path":"/var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount","volume_capability":{"AccessType":{"Mount":{"mount_flags":["-o ro","--virtual-directory=true","-o allow_other"]}},"access_mode":{"mode":3}},"volume_context":{"AzureStorageAuthType":"spn","AzureStorageSPNClientID":"stripped","AzureStorageSPNTenantID":"stripped","containerName":"frontend-bundle-reports","protocol":"fuse2","storageAccount":"stripped"},"volume_id":"frontend-storage-account#bundle-reports-container#handle"} I0417 08:11:47.086435 3245281 blob.go:416] volumeID(frontend-storage-account#bundle-reports-container#handle) authEnv: [AZURE_STORAGE_SPN_CLIENT_ID=stripped AZURE_STORAGE_SPN_TENANT_ID=stripped AZURE_STORAGE_AUTH_TYPE=spn] I0417 08:11:47.086472 3245281 nodeserver.go:355] target /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount protocol fuse2 volumeId frontend-storage-account#bundle-reports-container#handle context map[AzureStorageAuthType:spn AzureStorageSPNClientID:stripped AzureStorageSPNTenantID:stripped containerName:frontend-bundle-reports protocol:fuse2 storageAccount:stripped] mountflags [-o ro --virtual-directory=true -o allow_other] mountOptions [-o ro --virtual-directory=true -o allow_other --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true] args /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true serverAddress stripped.blob.core.windows.net I0417 08:11:47.086507 3245281 nodeserver.go:154] start connecting to blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true I0417 08:11:47.087040 3245281 nodeserver.go:163] begin to mount with blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true I0417 08:12:03.579849 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.600392 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.619859 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.640213 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.659613 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.679933 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.700365 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.719893 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.740316 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.759741 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.780055 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.799882 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.820254 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.839699 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.860090 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.879770 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.900304 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.919748 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.940218 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.959610 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.980062 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:03.999633 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.020185 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.039685 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.060184 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.079584 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.100014 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.120435 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.139790 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.160004 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.180415 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.199761 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.220146 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.239492 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.259878 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.280260 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.299939 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.320082 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.339431 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.359764 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.380109 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.399522 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.419931 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.440337 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.459658 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.479990 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.500452 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.519870 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.540280 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.559661 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.580050 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.599341 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.619634 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.640190 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.659502 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.739809 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.741290 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.759821 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.780311 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.799700 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.820180 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.839659 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.860114 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.879603 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.900123 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.919571 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.939946 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.960404 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:04.979826 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.000267 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.019781 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.040260 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.059719 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.080581 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.100020 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.120450 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.140314 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.159476 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.179754 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.200314 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.220129 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.239721 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.260444 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.280129 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.299617 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.320171 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.377586 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.379142 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.380458 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.399876 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.420301 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.439727 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.460122 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.479517 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.499890 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.520346 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.539734 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.560048 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.579566 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.600142 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.619743 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.640328 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.659791 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.680261 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.699862 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.720403 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.739831 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.760247 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.779615 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.799984 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.820436 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.839798 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.860178 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.879459 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.899768 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.920069 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.939445 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.959853 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.980306 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:05.999641 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.019991 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.040407 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.059846 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.080228 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.099778 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.120199 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.139586 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.174187 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.179410 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.199857 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.220102 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.239615 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.260059 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.279464 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.299867 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.320289 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.339703 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.360051 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.379340 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.399827 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.420205 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.439711 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.460167 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.479540 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.499941 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.520562 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:06.540065 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior E0417 08:12:06.558144 3245281 utils.go:80] GRPC error: failed to wait for mount: timeout waiting for mount /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount I0417 08:12:07.133026 3245281 utils.go:75] GRPC call: /csi.v1.Node/NodeStageVolume I0417 08:12:07.133044 3245281 utils.go:76] GRPC request: {"secrets":"***stripped***","staging_target_path":"/var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount","volume_capability":{"AccessType":{"Mount":{"mount_flags":["-o ro","--virtual-directory=true","-o allow_other"]}},"access_mode":{"mode":3}},"volume_context":{"AzureStorageAuthType":"spn","AzureStorageSPNClientID":"stripped","AzureStorageSPNTenantID":"stripped","containerName":"frontend-bundle-reports","protocol":"fuse2","storageAccount":"stripped"},"volume_id":"frontend-storage-account#bundle-reports-container#handle"} I0417 08:12:07.133529 3245281 blob.go:416] volumeID(frontend-storage-account#bundle-reports-container#handle) authEnv: [AZURE_STORAGE_AUTH_TYPE=spn AZURE_STORAGE_SPN_CLIENT_ID=stripped AZURE_STORAGE_SPN_TENANT_ID=stripped] I0417 08:12:07.133563 3245281 nodeserver.go:355] target /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount protocol fuse2 volumeId frontend-storage-account#bundle-reports-container#handle context map[AzureStorageAuthType:spn AzureStorageSPNClientID:stripped AzureStorageSPNTenantID:stripped containerName:frontend-bundle-reports protocol:fuse2 storageAccount:stripped] mountflags [-o ro --virtual-directory=true -o allow_other] mountOptions [-o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false] args /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false serverAddress stripped.blob.core.windows.net I0417 08:12:07.133577 3245281 nodeserver.go:154] start connecting to blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false I0417 08:12:07.133985 3245281 nodeserver.go:163] begin to mount with blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false E0417 08:12:22.853397 3245281 nodeserver.go:166] GRPC call returned with an error:rpc error: code = Unknown desc = exit status 1 Error: failed to daemonize application [daemon: Resource temporarily unavailable] E0417 08:12:22.853441 3245281 nodeserver.go:377] rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exit status 1 Error: failed to daemonize application [daemon: Resource temporarily unavailable] , output: I0417 08:12:22.853534 3245281 mount_linux.go:361] Unmounting /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount E0417 08:12:22.854910 3245281 utils.go:80] GRPC error: rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exit status 1 Error: failed to daemonize application [daemon: Resource temporarily unavailable] , output: I0417 08:12:23.915715 3245281 utils.go:75] GRPC call: /csi.v1.Node/NodeStageVolume I0417 08:12:23.915728 3245281 utils.go:76] GRPC request: {"secrets":"***stripped***","staging_target_path":"/var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount","volume_capability":{"AccessType":{"Mount":{"mount_flags":["-o ro","--virtual-directory=true","-o allow_other"]}},"access_mode":{"mode":3}},"volume_context":{"AzureStorageAuthType":"spn","AzureStorageSPNClientID":"stripped","AzureStorageSPNTenantID":"stripped","containerName":"frontend-bundle-reports","protocol":"fuse2","storageAccount":"stripped"},"volume_id":"frontend-storage-account#bundle-reports-container#handle"} I0417 08:12:23.916227 3245281 blob.go:416] volumeID(frontend-storage-account#bundle-reports-container#handle) authEnv: [AZURE_STORAGE_AUTH_TYPE=spn AZURE_STORAGE_SPN_CLIENT_ID=stripped AZURE_STORAGE_SPN_TENANT_ID=stripped] I0417 08:12:23.916271 3245281 nodeserver.go:355] target /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount protocol fuse2 volumeId frontend-storage-account#bundle-reports-container#handle context map[AzureStorageAuthType:spn AzureStorageSPNClientID:stripped AzureStorageSPNTenantID:stripped containerName:frontend-bundle-reports protocol:fuse2 storageAccount:stripped] mountflags [-o ro --virtual-directory=true -o allow_other] mountOptions [-o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false] args /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false serverAddress stripped.blob.core.windows.net I0417 08:12:23.916291 3245281 nodeserver.go:154] start connecting to blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false I0417 08:12:23.917058 3245281 nodeserver.go:163] begin to mount with blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --virtual-directory=true -o allow_other --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false I0417 08:12:39.674666 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior I0417 08:12:39.694049 3245281 mount_linux.go:283] Detected umount with safe 'not mounted' behavior ...
@kvet I could imagine where the problem is, in v1.19.3, we set 3s as mount timeout, usually 3s is enough, while in your case, it costs 18s for blobfuse2 mount. @vibhansa-msft do you know is there a possible reason why blobfuse2 mount took so long time? In the meantime, we will increase the 3s timeout as 30s at least in the CSI driver.
If this is new blobfuse version, then the fix to wait for the child mount to complete is embedded and now onwards we may see little more delay in mount completion. However, it shall be few seconds only and not in 10s. For any higher timeouts we shall look at the logs. We try to validate the connection with storage account if the response from server is slow for some reason, then mount will take that much time to complete as well.
@andyzhangx I found something suspicious in the blobfuse2 logs. Attaching them...
Is allow_other enabled here ? "mount: error unable to start pipeline [failed to mount fuse]" : this points to some issue in init of the libfuse library itself. Either you can enable log_debug and then try again or validate allow_other option is enabled in /etc/fuse.conf
@vibhansa-msft I am mounting the ABS container with the following mount options: -o allow_other -o ro --virtual-directory=true
I've also checked the node where the current blobfuse1 deployment is running (almost the same options but protocol: fuse
and no --virtual-directory=true
). And the /etc/fuse.conf
has the same contents.
Moreover, with the csi driver 1.19.2 on a fresh node (the one I am sending you the contents of /etc/fuse.conf
) I was able to start blobfuse2 once.
Can you please clarify what exact information you need me to provide in order to mitigate the issue? We are eager to use blobfuse2 as it performs way better in our use case.
We will need blobfuse logs to understand what took time during the mount operation. If you can enable log_debug and retry that might be useful.
When I started the new testing I noticed the new driver version had been deployed to our cluster. For which huge thank you, guys! And during my testing, I haven't experienced any issue with mounting and I can classify the original request as resolved. Hope it will work reliably.
Here are the logs from the new driver version and from a fresh node (to which no one blobfuse2 mount was done before). Hope it will help you to find out the root cause.
@kvet great to hear that.
Blobfuse logs shared above looks clean to me.
@kvet csi driver logs shows it's costing 27s to mount complete, and in v1.19.4, we set mount path timeout as 1min, that's why it works now:
I0417 14:26:30.977682 1067992 nodeserver.go:154] start connecting to blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --log-level=LOG_DEBUG --virtual-directory=true -o allow_other --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true
I0417 14:26:30.978212 1067992 nodeserver.go:163] begin to mount with blobfuse proxy, protocol: fuse2, args: /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount -o ro --log-level=LOG_DEBUG --virtual-directory=true -o allow_other --use-https=true --cancel-list-on-mount-seconds=10 --empty-dir-check=false --tmp-path=/mnt/frontend-storage-account#bundle-reports-container#handle --container-name=frontend-bundle-reports --pre-mount-validate=true
I0417 14:26:47.366271 1067992 mount_linux.go:283] Detected umount with safe 'not mounted' behavior
...many similar log messages...
I0417 14:26:57.966786 1067992 mount_linux.go:283] Detected umount with safe 'not mounted' behavior
I0417 14:26:57.966899 1067992 nodeserver.go:591] blobfuse mount at /var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount success
I0417 14:26:57.966917 1067992 nodeserver.go:409] volume(frontend-storage-account#bundle-reports-container#handle) mount on "/var/lib/kubelet/plugins/kubernetes.io/csi/blob.csi.azure.com/0996b15fb1f08f675cc4771ab8245e3b68ed7ed3abec8f2f45d196e3d33a1d43/globalmount" succeeded
Which version of blobfuse was used?
blobfuse2 version 2.0.2
Which OS distribution and version are you using?
AKS kernel version 1.23.12 Docker: FROM python:3.10.4
root@mydocker:/home# cat /proc/version Linux version 5.4.0-1091-azure (buildd@lcy02-amd64-023) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #96~18.04.1-Ubuntu SMP Tue Aug 30 19:15:32 UTC 2022
root@mydocker:/home# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
If relevant, please share your mount command.
install blobfuse2
wget https://packages.microsoft.com/config/debian/11/packages-microsoft-prod.deb dpkg -i packages-microsoft-prod.deb apt-get update apt-get install libfuse3-dev fuse3 -y apt-get install blobfuse2
mount command
blobfuse2 mount /home/blobfmount --config-file=/home/blobfuse2/config.yaml --container-name=mycontainer --log-level=log_debug --log-file-path=./bobfuse2b.log
here is config.yaml below:
Refer ./setup/baseConfig.yaml for full set of config parameters
allow-other: true
logging: type: syslog level: log_debug
components:
libfuse: attribute-expiration-sec: 120 entry-expiration-sec: 120 negative-entry-expiration-sec: 240
file_cache: path: /home/blobfuse/tempcache timeout-sec: 120 max-size-mb: 4096
attr_cache: timeout-sec: 7200
azstorage: type: block account-name: account-key: endpoint: container:
What was the issue encountered?
After I ran the blobfuse2 mount command, I cannot check the files in the destination blob or create test file and check in blob.
Have you found a mitigation/solution?
Not yet.
Please share logs if available.
root@mydocker:/home/blobfmount# cat bobfuse2b.log Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_CRIT [mount.go (384)]: Starting Blobfuse2 Mount : 2.0.2 on [Debian GNU/Linux 11 (bullseye)] Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_CRIT [mount.go (385)]: Logging level set to : LOG_DEBUG Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [libfuse.go (220)]: Libfuse::Configure : libfuse Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [libfuse.go (260)]: Libfuse::Configure : read-only false, allow-other true, default-perm 511, entry-timeout 120, attr-time 120, negative-timeout 240, ignore-open-flags: true, nonempty false Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [file_cache.go (197)]: FileCache::Configure : file_cache Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [file_cache.go (272)]: FileCache::Configure : Using default eviction policy Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [file_cache.go (291)]: FileCache::Configure : create-empty false, cache-timeout 120, tmp-path /home/blobfuse/tempcache, max-size-mb 4096, high-mark 80, low-mark 60 Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [attr_cache.go (121)]: AttrCache::Configure : attr_cache Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [attr_cache.go (145)]: AttrCache::Configure : cache-timeout 7200, symlink false, cache-on-list true Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [azstorage.go (83)]: AzStorage::Configure : azstorage Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [config.go (270)]: ParseAndValidateConfig : Parsing config Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [config.go (372)]: ParseAndValidateConfig : using the following proxy address from the config file: Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [config.go (376)]: ParseAndValidateConfig : sdk logging from the config file: false Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [config.go (479)]: ParseAndReadDynamicConfig : Reparsing config Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_DEBUG [config.go (383)]: ParseAndValidateConfig : Getting auth type Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [config.go (467)]: ParseAndValidateConfig : Account: mystorageaccount, Container: mycontainer, AccountType: BLOCK, Auth: KEY, Prefix: , Endpoint: https://mystorageaccount.blob.core.chinacloudapi.cn/, ListBlock: 0, MD5 : false false, Virtual Directory: true Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [config.go (471)]: ParseAndValidateConfig : Retry Config: Retry count 5, Max Timeout 900, BackOff Time 4, Max Delay 60 Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [block_blob.go (173)]: BlockBlob::SetupPipeline : Setting up Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [block_blob.go (135)]: BlockBlob::getCredential : Getting credential Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_DEBUG [azauth.go (79)]: azAuth::getAzAuth : Account: mystorageaccount, AccountType: BLOCK, Protocol: https, Endpoint: https://mystorageaccount.blob.core.chinacloudapi.cn/ Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [block_blob.go (260)]: BlockBlob::SetPrefixPath : path Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_TRACE [block_blob.go (209)]: BlockBlob::TestPipeline : Validating Wed Mar 8 06:31:11 UTC 2023 : blobfuse2[607] : LOG_INFO [mount.go (392)]: mount: Mounting blobfuse2 on /home/blobfmount root@mydocker:/home/blobfmount# cd ..
I tried to do an unmount command and returned this:
root@mydocker:/home# blobfuse2 unmount all Error: failed to list mount points [open /etc/mtab: no such file or directory] root@mydocker:/home# blobfuse2 mount /home/blobfmount --config-file=/home/blobfuse2/config.yaml --container-name=mycontainer --log-level=log_debug --log-file-path=./bobfuse2b.log Error: mount directory is not empty root@mydocker:/home# rm -f ./blobfuse2/* rm: cannot remove './blobfuse2/config.yaml': Device or resource busy root@mydocker:/home#