-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multi-attach #120
Comments
Multi-attach mount volumes would be problematic even on the single writer multiple readers scenario. There are filesystems (like NTFS, and Ext4) that would corrupt the volume when we mount them on multiple hosts, even if they are read only. We'll still have issues when we use other filesystems that don't have that issue, because Linux clients cache blocks locally, and they do not invalidate that cache. So we could experience application crashes when accessing data structures that were partially cached while being changed on the original. Ext4 replays the journal even on readonly mounts. So a readonly mount will still write to the underlying block device. It would be unsafe even if both the mounts were readonly. We could try attaching the volume as readonly (or setting it to RO with blockdev --setro) before mounting and see it if works for the all readers (and no writers) case. |
With this patch we now support RWX and ROX modes for block volumes, and we fail for mount volumes. Fix embercsi#120
With this patch we now support RWX and ROX modes for block volumes, and we fail for mount volumes. Fix embercsi#120
With this patch we now support RWX and ROX modes for block volumes, and we fail for mount volumes. Fix embercsi#120
With this patch we now support RWX and ROX modes for block volumes, and we fail for mount volumes. Fix embercsi#120
We should support multi-attach for block volumes even if we cannot support it for mount volumes.
The text was updated successfully, but these errors were encountered: