On Sep 22, 2016 8:18 AM, "Rich Freeman" <r-bt...@thefreemanclan.net> wrote: > > I have been getting panics consistently after doing a btrfs replace > operation on a raid1 and rebooting. I linked a photo of the panic; I > haven't been able to get a text capture of it. > > https://ibin.co/2vx0HhDeViu3.jpg > > I'm getting this error on the latest 4.4, 4.1, and even on an old > 3.18.26 kernel I had lying around.
Apologies for replying out of order, but I lost the reply (the downside to running btrfs on my mail server). I was also suspicious of memory but memtestx86 hasn't found anything in (though I haven't run it longer than 10min). Sysrescuecd is my normal rescue image and I haven't gotten that to panic, but I haven't tried to start any services from it. Unfortunately it is openrc based so getting systemd running on my btrfs image inside a container will be painful. Maybe I can find a systemd based rescue image that includes nspawn. I suspect I'll have the same issue though as several kernels have failed. I'll do more extensive RAM tests just in case. However, the consistency of the error messages suggests a bug to me. Rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
