What's the backtrace from the crashing OSDs? Keep in mind that as a dev release, it's generally best not to upgrade to unnamed versions like 0.82 (but it's probably too late to go back now). -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com
On Mon, Jun 30, 2014 at 8:06 AM, Pierre BLONDEAU <[email protected]> wrote: > Hi, > > After the upgrade to firefly, I have some PG in peering state. > I seen the output of 0.82 so I try to upgrade for solved my problem. > > My three MDS crash and some OSD triggers a chain reaction that kills other > OSD. > I think my MDS will not start because of the metadata are on the OSD. > > I have 36 OSD on three servers and I identified 5 OSD which makes crash > others. If i not start their, the cluster passe in reconstructive state with > 31 OSD but i have 378 in down+peering state. > > How can I do ? Would you more information ( os, crash log, etc ... ) ? > > Regards > > -- > ---------------------------------------------- > Pierre BLONDEAU > Administrateur Systèmes & réseaux > Université de Caen > Laboratoire GREYC, Département d'informatique > > tel : 02 31 56 75 42 > bureau : Campus 2, Science 3, 406 > ---------------------------------------------- > > > _______________________________________________ > ceph-users mailing list > [email protected] > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
