On Fri, Jun 3, 2016 at 9:37 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
[chris@f24m ~]$ sudo btrfs scrub status /
[sudo] password for chris:
scrub status for dbf2e938-1f28-4e93-aa6c-1e193004931b
scrub started at Fri Jun 3 20:38:15 2016, interrupted after
00:00:05, not running
total bytes scrubbed: 2.52GiB with 0 errors
The other problem is the journal doesn't contain any hint why there
was an interruption.
What this incentivizes me to do is just stay logged in, in cases where
I probably should log out. So the security enhancement claims for the
feature may be true, but I don't think it's taking into account the
potential for users to just remain logged in (with or without a lock
screen) which then obviates the security claims.