Re: What is the state of filestore sloppy CRC?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



According to XFS docs, setting crc=1 will only enable CRC validation of XFS metadata (ie. mtime, xattrs, etc.). Still, nothing guarantees integrity of the actual data.

2014-11-25 11:05 GMT+01:00 Denis Kaganovich <mahatma@xxxxxxxxxxxxxx>:
How about XFS journal crc (mkfs stage crc=1)? Somebody trying?

Tomasz Kuzemko писал 2014-11-25 13:01:
Hello,
as far as I can tell, Ceph does not make any guarantee that reads from
an object return what was actually written to it. In other words, it
does not check data integrity (except doing deep-scrub once every few
days). Considering the fact that BTRFS is not production-ready, not
many people use Ceph on top of ZFS, then the only option to have some
sort of guarantee of integrity is to enable "filestore sloppy crc"
option. Unfortunately the docs aren't too clear about this matter and
"filestore sloppy crc" is not even documented, which is weird
considering it's merged since Emperor.

Getting back to my actual question - what is the state of "filestore
sloppy crc"? Does someone actually use it in production? Are there any
considerations one should make before enabling it? Is it safe to
enable it on an existing cluster?

--

Tomasz Kuzemko
tomasz@xxxxxxxxxxx

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



--
Tomasz Kuzemko
tomasz@xxxxxxxxxxx
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux