I have had several crashes in Lustre 2112. In the shell there is a message indicating a “Segmentation Fault”. Crashes all happened working with Red files over wiretap. Any help would be appreciated. Thanks.
Michael

Hi Michael,

Segmentation faults are not a good sign. Have you called support and opened a case? That is the best place to start.

That said, how are you bringing the RED files into Lustre? You said via the WTG which is fine and I assume the RED files are sitting on your unmanaged storage rather than a USB drive.

How many slave processes do you have running for RED debayering?

This crashing is only with RED and not with other file formats? What more can you tell me about information in the shell when the crash happens? Is there a repeatable technique to make it crash?

Is this Lustre 2012 or Flame Premium 2012?

Paul

I’ve seen this on DPX renders too.
I think its a 2012 bug. I haven’t tested 2012 sp3 yet so I hope its been fixed in that.

Hello Michael,

I would definitely open a call with support and also make sure you are on the latest version 2012 SP3. Support would ask the same and then see if the system is still segmentation faulting.

Also, what debayer setting are you using? Quarter? Half Good? The reason I ask is I have seen Lustre crash if I am in Full Debayer of 4K and try to slam around the timeline. Things get choked up fast with all that data trying to stream. Then when you let go of the controls Lustre has to catch up. Sometimes it feels locked up but in fact it is trying to get your 4K material in the pipe.

That however is quite different than a segmentation fault. Support will also be interested in any extra info in the shell where that fault is noted. It can help point them in the direction of the problem.

As far as the amount of slaves go, 10 is typical for a Flame Premium.

Paul