One Hat Cyber Team

Your IP: 216.73.216.114
Server IP: 13.127.59.50
Server: Linux ip-172-31-46-210 5.15.0-1033-aws #37~20.04.1-Ubuntu SMP Fri Mar 17 11:39:30 UTC 2023 x86_64
Server Software: Apache/2.4.41 (Ubuntu)
PHP Version: 7.4.3-4ubuntu2.29
Buat File | Buat Folder

Edit File: TODO.Debian

debian mdadm TODO list
======================

- version-1 is a nightmare. E.g. on partitionable arrays, with / on
  /dev/md_d0p3, mdadm -Es ignores /dev/md_d0 and just uses the name, so
  /dev/md/<arrayname>.
- figure out something about device names.
- (better) udev integration

- check whether mdadm.conf and system are consistent during initramfs creation
  and fail otherwise (#381303).
- add code to compare existing and expected configuration, after standardising
  the files. In most cases, we'll have to answer DUNNO as to whether the
  existing configuration file is okay, but I guess in some cases we can
  determine that the configuration is okay. A conservative approach would be
  beneficial to the user. Not sure if it's worth the effort though.
- one nice^W important thing would be to check device names and UUIDs at least.

- verify operation without udev
  - udev removed before mdadm installed
  - udev removed after mdadm installed

- more granular handling of init.d starts/stops, don't force all arrays to be
  started.
- let user specify when to start/stop which array (#398310).
- also only stop those array we started; this can be easily done with
  sentinels in $STATEDIR

- manage DAEMON_OPTIONS with debconf