On Mon, Jul 31, 2017 at 2:39 AM, qi Shi <m13913886148@xxxxxxxxx> wrote: > 1, What causes pg incomplete ? > Is it because pg failed to select the authoritative log? > > 2, What causes pg inconsistent ? > When pg status is inconsistent, why don't peering but inconsistent ? > > 3, What's the difference between pg incomplete and pg inconsistent ? > > Can you analyze it from pg state machine? An incomplete PG is missing part of the log or modified objects it needs in order to go active. An inconsistent PG has detected via scrubbing that some of its objects differ when they should be the same. So an inconsistent PG is active because it has all the data it should, some of that data just doesn't make sense. An incomplete PG does not. (Also, if you're running a sufficiently old version of Ceph, a PG might be incomplete because there aren't enough live replicas — in current code that is called "undersized", though.) -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
