Merge branch 'blobfuse2' of https://github.com/normesta/azure-docs-pr into blobfuse2

Author: normesta

articles/storage/blobs/TOC.yml

@@ -486,7 +486,7 @@ items:
       - name: Reliability
         items:
           - name: Reliability in Azure Blob Storage
-            href: ../../reliability/reliability-storage-blob.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
+            href: /azure/reliability/reliability-storage-blob?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
           - name: Design highly available applications
             href: ../common/geo-redundant-design.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
           - name: "Tutorial: Design applications for high availability"
@@ -1329,8 +1329,6 @@ items:
             href: ../common/storage-compliance-offerings.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
   - name: Data Lake Storage
     items:
-<<<<<<< HEAD
-=======
     - name: Data protection
       href: data-protection-overview.md
     - name: Soft delete versus versioning
@@ -1934,7 +1932,6 @@ items:
       href: ../common/storage-samples.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
     - name: Azure PowerShell
       items:
->>>>>>> 2019f4cc91b7197a4ae8938490d15e5f197777a8
       - name: Overview
         items:
           - name: Introduction to Data Lake Storage

articles/storage/blobs/blobfuse2-compare-linux-file-system.md

@@ -1,49 +1,49 @@
 ---
-title: BlobFuse2 and Linux file systems compared
+title: BlobFuse and Linux file systems compared
 titleSuffix: Azure Storage
-description: Learn about the differences between a BlobFuse2 file system and a Linux file system.
+description: Learn about the differences between a BlobFuse file system and a Linux file system.
 author: normesta
 ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: reference
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 
-# Customer intent: "As a developer or system administrator using BlobFuse2, I want to understand how BlobFuse2-mounted storage differs from native Linux file systems, so that I can set proper expectations and avoid potential issues when working with blob data."
+# Customer intent: "As a developer or system administrator using BlobFuse, I want to understand how BlobFuse-mounted storage differs from native Linux file systems, so that I can set proper expectations and avoid potential issues when working with blob data."
 ---
 
-# BlobFuse2 and Linux file systems compared
+# BlobFuse and Linux file systems compared
 
-This article describes the similarities and differences between BlobFuse2 and native Linux file systems.
+This article describes the similarities and differences between BlobFuse and native Linux file systems.
 
-## Similarities between BlobFuse2 and Linux file systems
+## Similarities between BlobFuse and Linux file systems
 
-You can use BlobFuse2-mounted storage similarly to a native Linux file system. The virtual directory scheme uses the same forward slash (`/`) delimiter. Basic file system operations such as `mkdir`, `opendir`, `readdir`, `rmdir`, `open`, `read`, `create`, `write`, `close`, `unlink`, `truncate`, `stat`, and `rename` work the same as in a native Linux file system.
+You can use BlobFuse-mounted storage similarly to a native Linux file system. The virtual directory scheme uses the same forward slash (`/`) delimiter. Basic file system operations such as `mkdir`, `opendir`, `readdir`, `rmdir`, `open`, `read`, `create`, `write`, `close`, `unlink`, `truncate`, `stat`, and `rename` work the same as in a native Linux file system.
 
-## Differences between BlobFuse2 and Linux file systems
+## Differences between BlobFuse and Linux file systems
 
-- **Hard link count in readdir**: For performance reasons, BlobFuse2 doesn't correctly report the number of hard links inside a directory. The hard link count for empty directories always returns as 2, and for nonempty directories always returns as 3, regardless of the actual number of hard links.
+- **Hard link count in readdir**: For performance reasons, BlobFuse doesn't correctly report the number of hard links inside a directory. The hard link count for empty directories always returns as 2, and for nonempty directories always returns as 3, regardless of the actual number of hard links.
 
 - **Non-atomic renames**: Azure Blob Storage doesn't support atomic rename operations. Single-file renames are actually two operations: a copy followed by deletion of the original. Directory renames recursively enumerate all files in the directory and rename each file individually.
 
-- **Special files**: BlobFuse2 supports only directories, regular files, and symbolic links. Special files like device files, pipes, and sockets aren't supported.
+- **Special files**: BlobFuse supports only directories, regular files, and symbolic links. Special files like device files, pipes, and sockets aren't supported.
 
-- **mkfifo**: Fifo creation isn't supported by BlobFuse2. Attempting this action results in a "function not implemented" error.
+- **mkfifo**: Fifo creation isn't supported by BlobFuse. Attempting this action results in a "function not implemented" error.
 
-- **chown and chmod**: BlobFuse2 doesn't support `chown` operations for either block blob storage (FNS) or Data Lake Storage (HNS). FNS storage accounts don't support `chmod` operations. HNS storage accounts support `chmod` operations but only on child objects within the mount directory, not on the root mount directory itself.
+- **chown and chmod**: BlobFuse doesn't support `chown` operations for either block blob storage (FNS) or Data Lake Storage (HNS). FNS storage accounts don't support `chmod` operations. HNS storage accounts support `chmod` operations but only on child objects within the mount directory, not on the root mount directory itself.
 
-- **Device files or pipes**: BlobFuse2 doesn't support creating device files or pipes.
+- **Device files or pipes**: BlobFuse doesn't support creating device files or pipes.
 
-- **Extended-attributes (x-attrs)**: BlobFuse2 doesn't support extended-attributes (`x-attrs`) operations.
+- **Extended-attributes (x-attrs)**: BlobFuse doesn't support extended-attributes (`x-attrs`) operations.
 
 - **Write streaming**: Concurrent read and write operations on large files might produce unpredictable results. Writing to the same blob simultaneously from different threads isn't supported.
 
 ## Next steps
 
-- [Install BlobFuse2](blobfuse2-install.md)
-- [Configure BlobFuse2](blobfuse2-configure.md)
+- [Install BlobFuse](blobfuse2-install.md)
+- [Configure BlobFuse](blobfuse2-configure.md)
 - [Mount an Azure Blob Storage container](blobfuse2-mount-container.md)
 
 ## See also

articles/storage/blobs/blobfuse2-configuration.md

@@ -4,10 +4,11 @@ titleSuffix: Azure Storage
 description: Learn how to configure settings for BlobFuse.
 author: akashdubey-ms
 ms.author: akashdubey
+ms.reviewer: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/02/2022
+ms.date: 01/29/2026
 # Customer intent: "As a cloud administrator, I want to configure settings for BlobFuse, so that I can effectively manage access, logging, caching, and permissions in my deployment."
 ---
 
@@ -53,7 +54,7 @@ You also can set configuration settings when you pass them as parameters of the
 blobfuse2 mount ./mount_dir --config-file=./config.yaml --container-name=blobfuse2b --log-level=log_debug --log-file-path=./bobfuse2b.log
 ```
 
-For more information about the entire BlobFuse command set, including the `blobfuse2 mount` command, see [BlobFuse2 commands](blobfuse2-commands.md) and [BlobFuse2 mount commands](blobfuse2-commands-mount.md).
+For more information about the entire BlobFuse command set, including the `blobfuse2 mount` command, see [BlobFuse commands](blobfuse2-commands.md) and [BlobFuse2 mount commands](blobfuse2-commands-mount.md).
 
 ## Next steps
 

articles/storage/blobs/blobfuse2-configure-caching.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 
@@ -52,7 +52,7 @@ You can configure a temporary path on a local high performing disk, a RAM disk,
 
 If you use an existing local disk for caching, choose a disk that provides the best performance possible, such as a solid-state disk (SSD).
 
-In Azure, you can use the SSD ephemeral disks that are available on your virutal machines (VMs) to provide a low-latency buffer for BlobFuse. Depending on the provisioning agent you use, mount the ephemeral disk on `/mnt` for cloud-init or `/mnt/resource` for Microsoft Azure Linux Agent (waagent) VMs.
+In Azure, you can use the SSD ephemeral disks that are available on your virtual machines (VMs) to provide a low-latency buffer for BlobFuse. Depending on the provisioning agent you use, mount the ephemeral disk on `/mnt` for cloud-init or `/mnt/resource` for Microsoft Azure Linux Agent (waagent) VMs.
 
 Make sure that your user has access to the temporary path.
 
@@ -74,15 +74,16 @@ sudo chown <youruser> /mnt/ramdisk/blobfuse2tmp
 
 In caching mode, BlobFuse waits for an open file system call. Upon receiving the open call, BlobFuse downloads the entire file to a local cache before using it. This behavior can make the initial load slower, especially for AI and machine learning tasks where the application is processing many files.
 
-The preload feature helps by downloading entire containers or subdirectories to the local cache when you mount them. Preload enhances data availability, boosting efficiency and reducing wait times. This improvement is vital for AI training with large datasets as it prepares all necessary files in advance, saving GPU time and reducing costs. By combining preload with the blob filter feature, you can access specific files in a container or subdirectory, offering extensive flexibility and optimizing GPU cycles.
+The preload feature helps by downloading entire containers or subdirectories to the local cache when you mount them. Preload enhances data availability, boosting efficiency and reducing wait times. This improvement is vital for AI training with large datasets as it prepares all necessary files in advance, saving GPU time and reducing costs. By combining preload with the [Blob Filter](https://github.com/Azure/azure-storage-fuse/wiki/Blobfuse-Blob-Filter) feature, you can access specific files in a container or subdirectory, offering extensive flexibility and optimizing GPU cycles.
 
 To enable preload with file-cache mode, use the `--preload` parameter. The following command shows an example:
 
 ```bash
 blobfuse2 mount --preload /mnt/blobfuse_mnt --tmp-path=/home/temp_path 
 ```
 
-Preloading blob data makes the mount read-only and prevents file eviction. To access updated files, unmount and remount the volume. Newly added files can still be accessed by reading them. If a blob filter is used with preload, only the filtered files are preloaded and accessible via the BlobFuse mount.
+> [!NOTE]
+> Preloading blob data makes the mount read-only and prevents file eviction. To access updated files, unmount and remount the volume. Newly added files can still be accessed by reading them. If a blob filter is used with preload, only the filtered files are preloaded and accessible via the BlobFuse mount.
 
 ### Considerations when using the preload feature
 

articles/storage/blobs/blobfuse2-configure-streaming.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 

articles/storage/blobs/blobfuse2-configure.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 
@@ -24,26 +24,24 @@ This article shows you how to generate and customize a configuration file. After
 
 1. Decide whether you want to mount the container in _caching mode_ or _streaming mode_. See [Streaming versus caching mode](blobfuse2-streaming-versus-caching.md).
 
-1. Generate a configuration file by using the `gen-configuration` command.
+1. Generate a configuration file by using the `gen-config` command.
 
    The following example generates a configuration file for mounting a container in caching mode.
 
    ```bash
-   blobfuse2 gen-configuration --tmp-path=<local-cache-path> --o <path-to-save-generated-config>
+   blobfuse2 gen-config --tmp-path=<local-cache-path> --o <path-to-save-generated-config>
    ```
 
    The following example generates a configuration file for mounting a container in streaming mode.
 
    ```bash
-   blobfuse2 gen-configuration --streaming --o <path-to-save-generated-config>
+   blobfuse2 gen-config --block-cache --o <path-to-save-generated-config>
    ```
 
-   This generates a configuration file that contains default settings.
+   This generates a configuration file that contains default settings. If path is not provided, the config will be generated at the current path.
 
 1. Open the configuration file in an editor to review and modify settings.
 
-1. Depending on which mode you plan to use, remove either `block_cache` or `file_cache` from the **Pipeline configuration** section. If you plan to use caching mode, remove `block_cache` from the list. If you plan to use streaming mode, remove `file_cache` from the list.
-
 1. Configure caching or streaming mode.
 
    If you choose to mount a container in caching mode, modify the `file_cache` block of settings. The following snippet shows an example configuration.
@@ -85,15 +83,15 @@ This article shows you how to generate and customize a configuration file. After
 
 In addition, there are other optional configuration settings that you can use to fine-tune the mount. For details about the configuration options, see the [base sample configuration](https://github.com/Azure/azure-storage-fuse/blob/main/setup/baseConfig.yaml).
 
-You can override settings that you define in the configuration file by using environment variables or by passing parameters as part of the command. For more information about using environment variables and a list of all variables you can use, see the [BlobFuse README](https://github.com/Azure/azure-storage-fuse/tree/main#environment-variables).
+You can override settings that you define in the configuration file by using environment variables or by passing parameters as part of the command. For more information about using environment variables and a list of all variables you can use, see the [BlobFuse Environment Variables](https://github.com/Azure/azure-storage-fuse/wiki/Blobfuse2-Environment-Variables).
 
 ## Configuration file best practices
 
 - If you **don't provide** `type` in the `azstorage` section of the configuration file, BlobFuse autodetects the account type and sets the respective endpoint. Therefore, if you use private endpoints, you must expose the Data Lake Storage endpoint; otherwise, the mount fails.
 
 - If you **provide** `type` in the `azstorage` section of the configuration file, don't mount a hierarchical namespace enabled account with `type: block` in the `azstorage` section. Otherwise, some directory operations fail. Don't mount a flat namespace account with `type: adls` in the `azstorage` section. Otherwise, you receive mount failures.
 
-- To disable all forms of caching at the kernel and at the BlobFuse level, set the `-o direct_io` CLI parameter. This option forces every operation to call the storage service directly, ensuring you always have the most up-to-date data.
+- To disable all forms of caching at the kernel and at the BlobFuse level, set the `-o direct_io` CLI parameter or `direct-io: true' in libfuse section of configuration file. This option forces every operation to call the storage service directly, ensuring you always have the most up-to-date data.
 
   > [!WARNING]
   > This configuration leads to increased storage costs, as it generates more transactions.

articles/storage/blobs/blobfuse2-enable-logs.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 

articles/storage/blobs/blobfuse2-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: This article provides a list of frequently asked questions (FAQ) for Blob. 
   ms.topic: faq
   ms.service: azure-blob-storage
-  ms.date: 11/25/2024
+  ms.date: 1/29/2026
   ms.author: normesta
   author: normesta
 title: BlobFuse frequently asked questions

articles/storage/blobs/blobfuse2-health-monitor.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/02/2022
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 

articles/storage/blobs/blobfuse2-install.md

@@ -7,7 +7,7 @@ ms.author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 1/29/2026
 
 ms.custom: linux-related-content
 
@@ -26,7 +26,7 @@ First, check your Linux distribution and version by running the following comman
 cat /etc/*-release
 ```
 
-To determine if a package is available for your distribution and version, see [BlobFuse2 releases](https://github.com/Azure/azure-storage-fuse/releases).
+To determine if a package is available for your distribution and version, see [BlobFuse releases](https://github.com/Azure/azure-storage-fuse/releases).
 
 If no package is available for your distribution or version, you need to build the binary from source code. For detailed instructions, see the [Build the binaries from source code](#build-the-binaries-from-source-code) section of this article.
 
@@ -182,7 +182,7 @@ To build the optional health monitor binary, run the following command:
 
 - [Configure BlobFuse](blobfuse2-configure.md)
 - [Mount an Azure Blob Storage container](blobfuse2-mount-container.md)
-- [BlobFuse2 commands](blobfuse2-commands.md)
+- [BlobFuse commands](blobfuse2-commands.md)
 
 ## See also