You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -15,7 +15,7 @@ Mounting the file system to the pool makes accessing data easier and more effici
15
15
16
16
Also, you can choose the underlying file system to meet performance, throughout, and input/output operations per second (IOPS) requirements. You can independently scale the file system based on the number of compute nodes that concurrently access the data.
17
17
18
-
For example, you could use an [Avere vFXT](/azure/avere-vfxt/avere-vfxt-overview) distributed in-memory cache to support large movie-scale renders with thousands of concurrent render nodes that access on-premises source data. Or, for data that's already in cloud-based blob storage, you can use [BlobFuse](/azure/storage/blobs/storage-how-to-mount-container-linux) to mount the data as a local file system. BlobFuse is available only on Linux nodes except Ubuntu 22.04, but [Azure Files](/azure/storage/files/storage-files-introduction) provides a similar workflow and is available on both Windows and Linux.
18
+
For example, you could use an [Avere vFXT](/azure/avere-vfxt/avere-vfxt-overview) distributed in-memory cache to support large movie-scale renders with thousands of concurrent render nodes that access on-premises source data. Or, for data that's already in cloud-based blob storage, you can use [BlobFuse](/azure/storage/blobs/storage-how-to-mount-container-linux) to mount the data as a local file system. [Azure Files](/azure/storage/files/storage-files-introduction) provides a similar workflow to that of BlobFuse and is available on both Windows and Linux.
19
19
20
20
## Supported configurations
21
21
@@ -30,11 +30,9 @@ Batch supports the following virtual file system types for node agents that are
30
30
31
31
| OS Type | Azure Files share | Azure Blob container | NFS mount | CIFS mount |
32
32
|---|---|---|---|---|
33
-
| Linux |:heavy_check_mark:|:heavy_check_mark:*|:heavy_check_mark:|:heavy_check_mark:|
33
+
| Linux |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
34
34
| Windows |:heavy_check_mark:|:x:|:x:|:x:|
35
35
36
-
\*Azure Blob container isn't supported on Ubuntu 22.04.
37
-
38
36
> [!NOTE]
39
37
> Mounting a virtual file system isn't supported on Batch pools created before August 8, 2019.
40
38
@@ -47,7 +45,7 @@ When you use virtual file mounts with Batch pools in a virtual network, keep the
47
45
-**Azure Blob containers** require TCP port 443 to be open for traffic to and from the `storage` service tag. Virtual machines (VMs) must have access to `https://packages.microsoft.com` to download the `blobfuse` and `gpg` packages. Depending on your configuration, you might need access to other URLs.
48
46
49
47
-**Network File System (NFS)** requires access to port 2049 by default. Your configuration might have other requirements. VMs must have access to the appropriate package manager to download the `nfs-common` (for Debian or Ubuntu) or `nfs-utils` (for CentOS) packages. The URL might vary based on your OS version. Depending on your configuration, you might also need access to other URLs.
50
-
48
+
51
49
Mounting Azure Blob or Azure Files through NFS might have more networking requirements. For example, your compute nodes might need to use the same virtual network subnet as the storage account.
52
50
53
51
-**Common Internet File System (CIFS)** requires access to TCP port 445. VMs must have access to the appropriate package manager to download the `cifs-utils` package. The URL might vary based on your OS version.
@@ -104,7 +102,7 @@ You can use [Azure PowerShell](/powershell/) to mount an Azure Files share on a
104
102
```
105
103
106
104
1. Get the context for your Batch account. Replace the `<batch-account-name>` placeholder with your Batch account name.
@@ -195,15 +193,16 @@ To get log files for debugging, you can use the [OutputFiles](batch-task-output-
195
193
196
194
### Investigate mounting errors
197
195
198
-
If you get the following error when you try to mount an Azure file share to a Batch node, you can RDP or SSH to the node to check the related log files.
196
+
You can RDP or SSH to the node to check the log files pertaining to filesystem mounts.
197
+
The following example error message is possible when you try to mount an Azure file share to a Batch node:
199
198
200
199
```output
201
200
Mount Configuration Error | An error was encountered while configuring specified mount(s)
202
201
Message: System error (out of memory, cannot fork, no more loop devices)
203
202
MountConfigurationPath: S
204
203
```
205
204
206
-
If you receive this error, RDP or SSH to the node to check the related log files. The Batch agent implements mounting differently on Windows and Linux. On Linux, Batch installs the package `cifs-utils`. Then, Batch issues the mount command. On Windows, Batch uses `cmdkey` to add your Batch account credentials. Then, Batch issues the mount command through `net use`. For example:
205
+
If you receive this error, RDP or SSH to the node to check the related log files. The Batch agent implements mounting differently on Windows and Linux for Azure file shares. On Linux, Batch installs the package `cifs-utils`. Then, Batch issues the mount command. On Windows, Batch uses `cmdkey` to add your Batch account credentials. Then, Batch issues the mount command through `net use`. For example:
207
206
208
207
```powershell-interactive
209
208
net use S: \\<storage-account-name>.file.core.windows.net\<fileshare> /u:AZURE\<storage-account-name> <storage-account-key>
@@ -220,7 +219,7 @@ net use S: \\<storage-account-name>.file.core.windows.net\<fileshare> /u:AZURE\<
220
219
```output
221
220
CMDKEY: Credential added successfully.
222
221
System error 86 has occurred.
223
-
222
+
224
223
The specified network password is not correct.
225
224
```
226
225
@@ -262,15 +261,15 @@ If you can't use RDP or SSH to check the log files on the node, you can upload t
262
261
263
262
1. When the upload completes, download the files and open *agent-debug.log*.
264
263
265
-
1. Review the error messages, for example:
264
+
1. Review the error messages, for example:
266
265
267
266
```output
268
267
..20210322T113107.448Z.00000000-0000-0000-0000-000000000000.ERROR.agent.mount.filesystems.basefilesystem.basefilesystem.py.run_cmd_persist_output_async.59.2912.MainThread.3580.Mount command failed with exit code: 2, output:
269
-
268
+
270
269
CMDKEY: Credential added successfully.
271
-
270
+
272
271
System error 86 has occurred.
273
-
272
+
274
273
The specified network password is not correct.
275
274
```
276
275
@@ -286,9 +285,9 @@ If you can't diagnose or fix mounting errors, you can use PowerShell to mount th
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments