| Server IP : 195.201.23.43 / Your IP : 3.143.254.11 Web Server : Apache System : Linux webserver2.vercom.be 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 User : kdecoratie ( 1041) PHP Version : 7.1.33-63+ubuntu20.04.1+deb.sury.org+1 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/mdadm/ |
Upload File : |
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 debconfPrivate