forked from Ivasoft/objectivefs-docker-volume
The noocache bug workaround has to be always active
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
4
main.go
4
main.go
@@ -24,7 +24,6 @@ import (
|
||||
"os/user"
|
||||
"path"
|
||||
"path/filepath"
|
||||
"slices"
|
||||
"strconv"
|
||||
"strings"
|
||||
"sync"
|
||||
@@ -411,8 +410,9 @@ func (d *ofsDriver) Mount(r *volume.MountRequest) (*volume.MountResponse, error)
|
||||
// the mount point is properly initialized. If we check too early then something breaks in the
|
||||
// mount.objectivefs process and the mount forever stays in startup state returning "Input/output error"
|
||||
// for any filesystem interaction from us or other tools.
|
||||
// UPDATE: The bug seems present also without "noocache" if S3 connection is fast enough
|
||||
// HACK: Due to the bug we just wait a safe interval
|
||||
if i == 0 && slices.Contains(v.Opts, "noocache") {
|
||||
if i == 0 /*&& slices.Contains(v.Opts, "noocache")*/ {
|
||||
time.Sleep(1000 * time.Millisecond)
|
||||
}
|
||||
if isObjfs, err := isObjectiveFsMount(mountPath); err == nil && isObjfs {
|
||||
|
||||
Reference in New Issue
Block a user