Re: Does "ceph df" use "bogus" copies factor instead of (k, m) for erasure coded pool?

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

 



On Tue, 16 Apr 2019 at 17:05, Paul Emmerich <paul.emmerich@xxxxxxxx> wrote:
>
> No, the problem is that a storage system should never tell a client
> that it has written data if it cannot guarantee that the data is still
> there if one device fails.
[...]

Ah, now I got your point.

Anyways, it should be users' choice (with warning probably, but
still). I can easily
(but with heavy heart) remind what happened twice and not too long ago
when someone decided
"we better know what to do than users^W pilots do". Too many similar
decisions were and (still are)
popping up in IT industry too. Of course always "for good reasons" --
who'd have a doubt(?)...

Oh, and BTW -- is it not possible to change EC(2,1)'s 3/3 to 3/2 in
Luminous, is it?

-- 
End of message. Next message?
_______________________________________________
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]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux