: Johannes Klarenbeek; ceph-users@lists.ceph.com
Onderwerp: Re: [ceph-users] Storage, File Systems and Data Scrubbing
ceph-osd builds a transactional interface on top of the usual posix
operations so that we can do things like atomically perform an object
write and update the osd metadata. The current
On Tue, 27 Aug 2013, ker can wrote:
This was very helpful -thanks. However I'm still trying to reconcile this
with something that Sage mentioned a while back on a similar topic.
Apparently you can disable the journal if you're using btrfs. Is that
possible because btrfs takes care of things
ceph-osd builds a transactional interface on top of the usual posix
operations so that we can do things like atomically perform an object
write and update the osd metadata. The current implementation
requires our own journal and some metadata ordering (which is provided
by the backing
I think you are missing the distinction between metadata journaling and data
journaling. In most cases a journaling filesystem is one that journal's it's
own metadata but your data is on its own. Consider the case where you have a
replication level of two, the osd filesystems have journaling
I think you are missing the distinction between metadata journaling and data
journaling. In most cases a journaling filesystem is one that journal's it's
own metadata but your data is on its own. Consider the case where you have a
replication level of two, the osd filesystems have
Let me make a simpler case, to do ACID (https://en.wikipedia.org/wiki/ACID)
which are all properties you want in a filesystem or a database, you need a
journal. You need a journaled filesystem to make the object store's file
operations safe. You need a journal in ceph to make sure the object
