Short version: When systemd-logind login.conf KillUserProcesses=yes, and the user does "sudo btrfs scrub start" in e.g. GNOME Terminal, and then logs out of the shell, the user space operation is killed, and btrfs scrub status reports that the scrub was aborted. [1]
I think what's going on is the user space stuff is what's tracking the status and statistics, so when that process goes to status Z on logout, all of that accounting stops. But I can't tell if the kernel scrub code finishes. Those threads continue some time after btrfs user space process goes Z, but seems like not quite long enough to actually finish the scrub. Neither 'btrfs balance &' (I have not tried the background balance code in progs 4.7) nor 'btrfs replace start' appear to be likewise affected. The user process remains after logout and the task appears to complete without problems. So at the moment I'm only thinking scrub is affected, but I'm not sure why. [1] systemd KillUserProcesses=yes and btrfs scrub https://bugzilla.kernel.org/show_bug.cgi?id=150781 -- Chris Murphy -- 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
