kdave
kdave
Setting the milestone to 4.14 was too optimistic. I've added the btrfs-ioctl page skeleton with some examples, so we can add the text incrementally.
https://patchwork.kernel.org/patch/9930323/ + other patches in the mailingist
Initial support added to devel, --rootdir + --subvol will fill the given subvolume. The final semantics will be something like this: ``` Sounds good, I think we can achieve more...
Unfortunatelly this won't work as expected. The ionice priority does not apply to the the threads that do the IO or CPU load as this is asynchronous and done by...
I'm not sure if the on_ac_power is generally available, so we'll need some fallback anyway, but systemd has `/usr/lib/systemd/systemd-ac-power` so we can cover most cases I think.
So the way you implement it in https://github.com/kdave/btrfsmaintenance/pull/45/commits/14c44e9d6e9ccfe6be5bcae42fd4cfa80480f35e it will just wait for AC and if it does not show up, the task continues. Is this desired from the user's...
-dusage=0 is not necessary because kernel does that automatically
The `exit 0` overriedes the last exit code, which is call to the logging facility (systemd-cat, cat, logger), so I'm not sure this is what your monitoring is interested in....
With the default it's hard to please everybody. The load caused by scrub has appeared after the CFQ (io scheduler) has been replaced by mq-deadline that does not implement `ionice`...
I think it should be possible to do with some systemd.service magic and script handling eg. signals.