22 Jul
2017
22 Jul
'17
22:11
Well, seems like the "lazy_itable_init" feature of mkfs.ext4 that Jan mentioned on the other thread (https://lists.opensuse.org/opensuse/2017-07/msg00867.html) was all that was causing the issue in the end. The drive started behaving shortly after I propagated this panic post this morning. It just needed more time. At least I hope that's all it was. Cheers, gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org