linux ghost compatibility with s3fs-fuse version 1.90

book

Article ID: 223065

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

s3fs-fuse version 1.90 had updates to its driver as expressed below

Version 1.90 -- 07 Aug, 2021 (major changes only)
#1599 - Don't ignore nomultipart when storage is low
#1600 - #1602 - #1604 - #1617 - #1619 - #1620 - #1623 - #1624 - Fix POSIX compatibility issues found by pjdfstest
#1630 - Fail CheckBucket when S3 returns PermanentRedirect
#1640 - #1655 - Do not create zero-byte object when creating file
#1648 - Allow arbitrary size AWS secret keys
#1668 - #1678 - Fix race conditions
#1696 - Set explicit Content-Length: 0 when initiating MPU
#1681 - Set CURLOPT_UNRESTRICTED_AUTH when authenticating
#1723 - Add jitter to avoid thundering herd
#1728 - Loosen CheckBucket to check only the bucket
#1729 - Add support for AWS-style environment variables

Cause

While client is is automation take a look at the /var/syslog file
using s3fs v.90 error shows:

s3fs[4647]: [tpath=/directory/directory_blah/blah.gho/][bpath=][save=][sseckeypos=18446744073709551615]

With previous version of s3fs (v1.89) the line looks like

s3fs[4647]: [tpath=/directory/directory_blah/blah.gho/][bpath=][save=][sseckeypos=-1]

In version 1.89, ssekey_pos is of type int
In version 1.90, they changed ssekey_pos to type size_t

Current hypothesis is the huge value for sseckeypos is causing Ghost to error.  (Normally sseckeypos has positive value only if custom server site encryption is being used.)

Environment

Release : 3.3

Component :

Resolution

At this time Ghost will not work with s3fs-fuse version 1.90