Failures in Mounting a Parallel File System

Symptom 1: "The specified bucket does not exist" or Similar Errors Occur

Fault Locating

The parallel file system to be mounted does not exist.

Solution

Create a parallel file system and mount it again. For details about how to create a parallel file system, see Creating a Parallel File System.

Symptom 2: "file system not support this request: this bucket not support filesystem" or Similar Errors Occur

Fault Locating

The mounted bucket is not a parallel file system.

Solution

Create a parallel file system and mount it again. For details about how to create a parallel file system, see Creating a Parallel File System.

Symptom 3: "The request signature we calculated does not match the signature you provided. Check your key and signing method." or Similar Errors Occur

Fault Locating

Authentication failed. The access keys (AK and SK) are incorrect.

Solution

Check whether the AK and SK information in the key file is correctly configured. For details about the check method, see 3 in the section "Initializing obsfs."

Symptom 4: "specified passwd_file is not readable" or Similar Errors Occur

Fault Locating

The key file path configured in the passwd_file file is incorrect.

Solution

Check whether the key file path configured in the passwd_file file is correct. For details about the check method, see 3 in the section "Initializing obsfs."

Symptom 5: "Access Denied" or Similar Errors Occur

Fault Locating

Authentication failed. The IAM user does not have OBS operation permissions.

Solution

Authorize the user with required OBS operation permissions. For details, see Resource Preparation.

Symptom 6: "unable to access MOUNTPOINT /obsfs: Transport endpoint is not connected" or Similar Errors Occur

Fault Locating

The mount point is occupied by another obsfs mount process.

Solution

Run the df command to query the partitions and points that have been mounted to. Then select an unoccupied mount point and mount the bucket again.

Symptom 7: "unknown option" or Similar Errors Occur

Fault Locating

One or more parameters in the mount command are incorrectly set and therefore failed to be identified by obsfs.

Solution

Check the mount parameters by referring to Table 1 in the section "Mounting the Parallel File System".

Symptom 8: "unable to access MOUNTPOINT /mnt/obsfs: No such file or directory" or Similar Errors Occur

Fault Locating

The mount directory does not exist.

Solution

Use the mkdir command to create a directory or mount the bucket to an existing directory.

Symptom 9: "device not found" or Similar Errors Occur

Fault Locating

1. The fuse component is not started.
2. In Docker container scenarios, parameter --privileged is missing.

Solution

1. Run the find / -name libfuse.so* command to check whether the fuse component is installed. If the component is not installed, install it by referring to the runtime environment configuration in Downloading and Installing obsfs.
2. Add parameter --privileged to the docker run command.

Symptom 10: "The difference between the request time and the current time is too large." or Similar Errors Occur

Fault Locating

There was a huge time offset between the system and the storage server, which made the request authentication fail.

Solution

Calibrate the system time.