Chris Murphy posted on Sat, 30 Jul 2016 14:02:17 -0600 as excerpted: > 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]
What does btrfs scrub resume do? Resume, or error? If it resumes, I'd say RESOLVED/NOTABUG as both that systemd option and btrfs scrub appear to be working as intended. If it doesn't, then there's definitely a btrfs bug, even if you argue it's only in the documentation, because the manpage (tho still 4.6.1, here) says it resumes an interrupted scrub but won't start a new one if the scrub finished successfully, and an abort is definitely an interruption, not a successful finish. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
