Your message dated Mon, 23 Dec 2024 15:33:23 +0000
with message-id
<CAJ3BuoTDfYvtPr8yG4Sec=RCU4hO6aCHOq_t=pGV=ptz61m...@mail.gmail.com>
and subject line Re: Bug#987069: document which file systems support cgroupv2
I/O controller
has caused the Debian Bug report #987069,
regarding document which file systems support cgroupv2 I/O controller
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
987069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal
Hi,
Last I checked, only btrfs supports the cgroupv2 I/O controller; this
should probably be documented. Alternatively, if more than btrfs (ie:
XFS and ext4) supports it, but not other file systems (ie: f2fs,
reiser4, jfs, etc) than this should be documented.
As far as I can tell, the significance of this is as follows: Buster
switched to mq-deadline, which does not support the idle I/O priority,
and to get functional ionice the user/sysadmin had to switch to the
non-mq CFQ, or bfq. The situation in a default Bullseye install is
better, but only for file systems that support the cgroupv2 I/O
controller.
Regards,
Nicholas
--- End Message ---
--- Begin Message ---
On Thu, 27 May 2021 09:44:37 +0200 Paul Gevers <elb...@debian.org> wrote:
> On 14-05-2021 05:04, Theodore Ts'o wrote:
> > On Thu, May 13, 2021 at 04:38:18PM -0400, Nicholas D Steeves wrote:
> >>> On 17-04-2021 00:35, Nicholas D Steeves wrote:
> Theodore, thanks for the extensive reply, I hope it helped Nicholas and
> I learned a bit from it. However, I'm very unsure what to do with all
> this (high quality) information as it seems not really in scope to talk
> about in the release notes and if it is, it's way too long. @Nicholas, I
> suggest you turn this bug into a Wiki page (assuming Theodore is fine
> with that) or something like that to expose this information to a
> broader audience. If after doing that, you still think there's something
> relevant to mention in the release notes, we'd have a place to point at
> for more background information and can keep the release note short. In
> that case, similar to your other bug report about cgroups, I'd
> appreciate a (draft) proposal for text to include.
Closing this bug, which relates to an older release, per discussion in
https://lists.debian.org/debian-doc/2024/12/msg00001.html
People who want cgroup2 I/O controller support are presumably using a
newer release by now
--- End Message ---
