Hi, Le 27/10/2016 à 01:54, Lionel Bouton a écrit : > > I'll post the final result of the btrfs replace later (it's currently at > 5.6% after 45 minutes).
Result : kernel panic (so 4.8.4 didn't solve my main problem). Unfortunately I don't have a remote KVM anymore so I couldn't capture this one. panic=60 however did its job twice (I tried to mount the filesystem again) confirming that a panic occured. It seems the problem may be located at a precise location. Yesterday the last replace resume logged : Oct 26 00:40:56 zagreus kernel: BTRFS info (device sdb2): continuing dev_replace from <missing disk> (devid 7) to /dev/sdb2 @12% And today I was switching between a screen terminal windows when the crash happened and the replace was at 12.6%. A mount triggers the crash in ~20 seconds which is similar to what happened yesterday on the last try. I've successfully canceled the replace to get back a usable system. I'll stop for tonight and see what happens during the day. I'd like to try a device add / delete next but I'm worried I could end up with a completely unusable filesystem if the device delete hits the same problem than replace. If the replace resuming on mount crashes the system I can cancel it but there's no way to do so with a device delete. Or is by any chance the skip_balance mount option a way to cancel a delete ? Best regards, Lionel -- 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
