You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users running on a Mac OS Ventura with an external SSD on a exFAT filesystem are unable to startup and run Prysm. This is due to the ENOTTY being returned by the OS on fsync calls.
Since prysm doesn't handle fsync calls directly with the OS, this would have to be fixed in bbolt which is upstream so that users can continue running on exFAT filesystems.
Has this worked before in a previous version?
Yes, on Mac OS Monterrey .
🔬 Minimal Reproduction
Run the latest version of Prysm on Mac OS Ventura with an external SSD (exFAT)
🔥 Error
file sync error: sync /path/to/data/directory: inappropriate ioctl for device
🌍 Your Environment
Operating System:
Mac OS Ventura 13.0
What version of Prysm are you running? (Which release)
v3.2.1
Anything else relevant (validator index / public key)?
N.A
The text was updated successfully, but these errors were encountered:
🐞 Bug Report
Description
Users running on a Mac OS Ventura with an external SSD on a exFAT filesystem are unable to startup and run Prysm. This is due to the ENOTTY being returned by the OS on fsync calls.
https://cs.opensource.google/go/go/+/refs/tags/go1.20.1:src/syscall/zerrors_darwin_amd64.go;l=1210
https://cs.opensource.google/go/go/+/refs/tags/go1.20.1:src/syscall/zerrors_darwin_amd64.go;l=1307
Similar errors have been reported in the following repos:
restic/restic#4016
restic/rest-server#198
realm/realm-core#5789
Since prysm doesn't handle
fsync
calls directly with the OS, this would have to be fixed inbbolt
which is upstream so that users can continue running onexFAT
filesystems.Has this worked before in a previous version?
Yes, on Mac OS Monterrey .
🔬 Minimal Reproduction
Run the latest version of Prysm on Mac OS Ventura with an external SSD (exFAT)
🔥 Error
🌍 Your Environment
Operating System:
Mac OS Ventura 13.0
What version of Prysm are you running? (Which release)
v3.2.1
Anything else relevant (validator index / public key)?
N.A
The text was updated successfully, but these errors were encountered: