Agata Kruszona-Zawadzka

This has our attention, but STRICT mode for labels currently has priority, and since this issue is not trivial, it needs its own time and attention, which is slotted after...

Sounds very strange. I'm setting up our test mfs3 instance right now to have storage class like yours and I will try to repeat your steps.

I tried to repeat your steps and it works for me. To be exact: - I have 6 chunkservers, 2 with label C, 4 with label D - I have...

Forgot to ask: are your chunks really missing? Or just invalid/wrong version?

Original class makes absolutely no difference, once files are moved to the new class, there is no information about the old class. The only "consequence" of the old class is...

@onlyjob no, it doesn't. It will remove 1 copy of data and try to replicate the other copy to the correct label - independently. MooseFS kind of tries to keep...

MooseFS does not assume any levels of safety on underlying storage, in that it deems them all safe or un-safe to the same degree. So it does not care that...

Using one copy and strict storage classes is using MooseFS in an unsafe manner. Yes, achieving both targets of replication in the same step would be better, that's why I...

@inkdot7 this section of the manual only describes what happens at creation time. However, if you look into the manpage of `mfsscadmin` command, you will find a table there: ```...

@inkdot7 You are right, strict mode is applied always to the whole class definition. Actually, you raised an interesting point and we had a short discussion about it. We made...