Mengatasi S3QL Error “Backend reports that fs is still mounted elsewhere, aborting”

Beberapa hari yang lalu, saya mengalami kendala disalah satu server yang memiliki moutingan disk menggunakan S3QL. Dimana ketika mau di mouting ulang, muncul pesan error “Backend reports that fs is still mounted elsewhere, aborting” lebih tepatnya seperti berikut ini

root@server:~# mount.s3ql s3://nama-bucket/ /mnt/nama-bucket --allow-other
Using 8 upload threads.
Autodetected 524232 file descriptors available for cache entries
Ignoring locally cached metadata (outdated).
Backend reports that fs is still mounted elsewhere, aborting.

Setelah di cek di beberapa forum, error tersebut biasanya dikarenakan melakukan reboot/shutdown server tanpa unmouting file system S3QL yang termounting terlebih dahulu, sehingga ketika dilakukan mount ulang, dianggap file system masih termounting di tempat lain.

Baca Juga : Mengatasi File System Damaged  Ketika Mounting Storage S3

Untuk eskalasinya, silakan lakukan fsck dengan perintah seperti berikut

fsck.s3ql s3://nama-bucket

Nanti akan ditanyakan konfirmasi seperti berikut, ketik continue kemudian tekan Enter, maka proses fsck akan berjalan, untuk berapa lamanya tergantung dari banyaknya data

Starting fsck of s3://nama-bucket/
Ignoring locally cached metadata (outdated).
Backend reports that file system is still mounted elsewhere. Either
the file system has not been unmounted cleanly or the data has not yet
propagated through the backend. In the later case, waiting for a while
should fix the problem, in the former case you should try to run fsck
on the computer where the file system has been mounted most recently.
Enter "continue" to use the outdated data anyway:
continue

Ini proses fscknya, tunggu hingga selesai

Downloading and decompressing metadata...
Reading metadata...
..objects..
..blocks..
..inodes..
Creating temporary extra indices...
Checking lost+found...
Checking cached objects...
Checking names (refcounts)...
Checking contents (parent inodes)...
Checking objects (reference counts)...
Checking objects (backend)...
Backing up old metadata...
Cleaning up local metadata...
Completed fsck of s3://nama-bucket

Jika sudah completed, silakan mounting kembali menggunakan S3QL, semestinya saat ini sudah bisa dimounting.

root@server:~# mount.s3ql s3://nama-bucket /mnt/nama-bucket --allow-other
Using 8 upload threads.
Autodetected 524232 file descriptors available for cache entries
Using cached metadata.
Setting cache size to 80235 MB
Mounting filesystem...

Di akhir postingan ini, ada sedikit pesan dari si developer S3QL ini 😀

• Jadi apapun kendala yang dialami saat menggunakan S3QL, pasti 99% bisa diatasi dengan menjalankan fsck.s3ql 😀
• Jangan shutdown server ketika file system S3QL masih termounting pada server

Mungkin cukup sekian, semoga bermanfaat