Le 22/07/2015 21:17, Lincoln Bryant a
écrit :
Hi Hadi, Yes it is, for several reasons. Here are two at the top of my head. Some (many/most/all?) filesystems update on-disk data when they are mounted even if the mount is read-only. If you map your RBD devices read-only before mounting the filesystem itself read-only you should be safe from corruption occurring at mount time though. The system with read-write access will keep its in-memory data in sync with the on-disk data. The others with read-only access will not as they won't be aware of the writes done, this means they will eventually get incoherent data and will generate fs access errors with various levels of errors from the benign read error to potentially full kernel crash with whole filesystem freeze in-between. Don't do that unless you : - carefully setup your rbd mappings read-only everywhere but the system doing the writes, - can withstand a (simultaneous) system crash on all the systems mounting the rbd mappings read-only. Lionel |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com