OBS Bucket or Parallel File System Mount Failures

"The specified bucket does not exist" or Similar Errors Occur

Fault Diagnosis

The parallel file system to be mounted does not exist.

Solution

• Check whether the entered name of the parallel file system is correct.
• Create a parallel file system and mount it again. For details, see Creating a Parallel File System.

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

Fault Diagnosis

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.

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

Fault Diagnosis

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."

"specified passwd_file is not readable" or Similar Errors Occur

Fault Diagnosis

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

Solution

Check whether the key file path configured in passwd_file is correct, whether the key file is missing, whether the current user lacks read permissions, and whether the path contains symbolic links. For troubleshooting details, see 3.

"Access Denied" or Similar Errors Occur

Fault Diagnosis

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.

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

Fault Diagnosis

The mount point is occupied by another obsfs process, or the FUSE kernel module is not running properly.

• The obsfs process may have crashed while the mount point remains. In this case, run fusermount -u /path/to/mountpoint, perform the mount again, and check whether the mount succeeds.
• The FUSE kernel module may not be loaded.
• /dev/FUSE may be missing.

Solution

Run the df command to check the mounted partitions and directories. Then choose an unoccupied directory and perform the mount again. Before the check, ensure that the mount point used by the process has been properly unmounted and that the FUSE dependency is correctly installed.

"unknown option" or Similar Errors Occur

Fault Diagnosis

One or more parameters in the mount command are misconfigured, causing obsfs to fail to recognize them.

Solution

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

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

Fault Diagnosis

The mount directory does not exist.

Solution

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

"device not found" or Similar Errors Occur

Fault Diagnosis

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 Method 1: Downloading and Installing obsfs.
2. Add parameter --privileged to the docker run command.

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

Fault Diagnosis

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

Solution

Calibrate the system time.

"credentials file should not have others/group permissions." or Similar Errors Occur

Fault Diagnosis

The key file permission is not 600.

Solution

Run the chmod command to change the permissions on the key file to 600.

"Check bucket failed." or Similar Errors Occur

Fault Diagnosis

If the logs contain a curl code, use that code to troubleshoot the issue. The code follows the libcurl error-code specifications. For example, curl code 6 indicates a DNS lookup failure or an incorrect endpoint URL, curl code 7 indicates a network failure or firewall blockage, and curl code 60 indicates an SSL certificate verification failure.

Solution

Run the chmod command to change the permissions on the key file to 600.