Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
All of these have status R and D for their duration, and while all get a SIGKILL from systemd on logout, none of the processes change status or die until their kernel task is done. And each of these operations complete successfully with no worse for the wear. btrfs balance & btrfs dev rem & btrfs

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
Aug 01 09:29:59 localhost.localdomain sudo[1875]:chris : TTY=pts/1 ; PWD=/home/chris ; USER=root ; COMMAND=/sbin/btrfs scrub start /mnt/x Aug 01 09:30:16 localhost.localdomain systemd[1]: user@1000.service: Killing process 1883 (btrfs) with signal SIGKILL. Aug 01 09:43:34 localhost.localdomain

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
On Mon, Aug 1, 2016 at 11:19 AM, Austin S. Hemmelgarn wrote: > On 2016-08-01 13:15, Chris Murphy wrote: >> I've been using balance with &, and when I logout, the btrfs command >> continues to flip between status D and R, just like before logout and >> it appears to

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Austin S. Hemmelgarn
On 2016-08-01 13:15, Chris Murphy wrote: On Mon, Aug 1, 2016 at 10:58 AM, Austin S. Hemmelgarn wrote: On 2016-08-01 12:19, Chris Murphy wrote: On Mon, Aug 1, 2016 at 10:08 AM, Austin S. Hemmelgarn wrote: MD and DM RAID handle this by starting

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
On Mon, Aug 1, 2016 at 10:58 AM, Austin S. Hemmelgarn wrote: > On 2016-08-01 12:19, Chris Murphy wrote: >> >> On Mon, Aug 1, 2016 at 10:08 AM, Austin S. Hemmelgarn >> wrote: >> >>> >>> MD and DM RAID handle this by starting kernel threads to do the

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Austin S. Hemmelgarn
On 2016-08-01 12:19, Chris Murphy wrote: On Mon, Aug 1, 2016 at 10:08 AM, Austin S. Hemmelgarn wrote: MD and DM RAID handle this by starting kernel threads to do the scrub. They then store the info about the scrub in the array itself, so you can query it externally. If

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
On Mon, Aug 1, 2016 at 10:19 AM, Chris Murphy wrote: > So that makes me wonder how btrfs device add and remove will behave, > if issued in a DE which is then logged out of. Those commands do not > return to prompt until they complete. Strike add. That's fast. I'm

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
On Mon, Aug 1, 2016 at 10:08 AM, Austin S. Hemmelgarn wrote: > > MD and DM RAID handle this by starting kernel threads to do the scrub. They > then store the info about the scrub in the array itself, so you can query it > externally. If you watch, neither of those commands

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Austin S. Hemmelgarn
On 2016-08-01 11:46, Chris Murphy wrote: OK I've created a new volume that's sufficiently large I can tell if the kernel workers doing the scrub are also being killed off. First, I do a scrub without logging out to get a time for an uninterrupted scrub. And then initiate a scrub which I start

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
On Mon, Aug 1, 2016 at 9:46 AM, Chris Murphy wrote: > - The kernel workers are killed off within ~5 seconds of an > uninterrupted scrub. i.e. the kernel workers are doing the same work. They aren't being killed sooner as a result of logging out from the DE. The only

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Chris Murphy
OK I've created a new volume that's sufficiently large I can tell if the kernel workers doing the scrub are also being killed off. First, I do a scrub without logging out to get a time for an uninterrupted scrub. And then initiate a scrub which I start timing, but then logout of the DE and watch

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-08-01 Thread Austin S. Hemmelgarn
On 2016-07-30 20:29, Chris Murphy wrote: On Sat, Jul 30, 2016 at 2:02 PM, Chris Murphy wrote: Short version: When systemd-logind login.conf KillUserProcesses=yes, and the user does "sudo btrfs scrub start" in e.g. GNOME Terminal, and Same thing with Xfce, so it's not

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-07-31 Thread Duncan
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

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-07-31 Thread Chris Murphy
On Sun, Jul 31, 2016 at 4:56 AM, Gabriel C wrote: > > > On 30.07.2016 22:02, Chris Murphy wrote: >> 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,

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-07-31 Thread Gabriel C
On 30.07.2016 22:02, Chris Murphy wrote: > 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

Re: systemd KillUserProcesses=yes and btrfs scrub

2016-07-30 Thread Chris Murphy
On Sat, Jul 30, 2016 at 2:02 PM, Chris Murphy wrote: > Short version: When systemd-logind login.conf KillUserProcesses=yes, > and the user does "sudo btrfs scrub start" in e.g. GNOME Terminal, and Same thing with Xfce, so it's not DE specific. (Unsuprising.) I inflated