Your message dated Sun, 06 Sep 2015 19:35:10 +0000 with message-id <[email protected]> and subject line Bug#620095: fixed in sysconfig 0.0.10+nmu2 has caused the Debian Bug report #620095, regarding DASD device configured via sysconfig-hardware cannot be varied offline 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 [email protected] immediately.) -- 620095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620095 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sysconfig-hardware Version: 0.0.10 Severity: normal When a DASD device is configured via sysconfig-hardware, it cannot be varied offline. (Strictly speaking, it can be varied offline, but it then comes back online again immediately.) I have been plagued with this bug for a long time (see archived Debian bug report 499833), but I have finally found the cause. The bug is in a udev rule provided by the sysconfig-hardware package. The file names are /lib/udev/rules.d/85-sysconfig-hardware.rules /etc/udev/rules.d/85-sysconfig-hardware.rules The two files are identical. As currently packaged, the file looks like this: SUBSYSTEM=="ccw", WAIT_FOR_SYSFS="online" SUBSYSTEM=="ccw", RUN+="/sbin/hwup -A -D $devpath $env{SUBSYSTEM} $kernel" The first rule doesn't seem to be causing a problem, but the second rule is definitely in error. The second rule will match any ACTION value (add, change, remove, etc.). It should only match the "add" action. Thus, this file should look like this: SUBSYSTEM=="ccw", WAIT_FOR_SYSFS="online" SUBSYSTEM=="ccw", ACTION=="add", RUN+="/sbin/hwup -A -D $devpath $env{SUBSYSTEM} $kernel" The above change must be made to both copies of the file: one in /lib/udev/rules.d and one in /etc/udev/rules.d. (I'm not sure why the exact same file has to exist in both places, but that is how things are currently set up.) I have tested this on my system. The devices are still brought online at boot time, as they were before; but now a device configured by sysconfig-hardware can be varied offline after booting (if one can get it unmounted). For example, umount /boot echo 0 >/sys/bus/ccw/devices/0.0.0201/online Note: the original example in Debian bug report 499833 is a poor example. I now use the regular ECKD or FBA driver for the /boot partition all the time. But there are other reasons to take a device offline while the system is running. For example, maybe the disk is full and you need to replace it with a larger one. -- .''`. Stephen Powell : :' : `. `'` `-
--- End Message ---
--- Begin Message ---Source: sysconfig Source-Version: 0.0.10+nmu2 We believe that the bug you reported is fixed in the latest version of sysconfig, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern <[email protected]> (supplier of updated sysconfig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 06 Sep 2015 09:27:57 +0200 Source: sysconfig Binary: sysconfig-hardware Architecture: source s390x Version: 0.0.10+nmu2 Distribution: unstable Urgency: medium Maintainer: Bastian Blank <[email protected]> Changed-By: Philipp Kern <[email protected]> Description: sysconfig-hardware - Hardware configuration Closes: 620095 620126 620205 795954 Changes: sysconfig (0.0.10+nmu2) unstable; urgency=medium . * Porter NMU. * Only run hwup from udev if devices are added. (Closes: #620095) Thanks to Stephen Powell for the hint. * 3880 storage control units support 3370 (FBA) and 3380 (CKD) devices. The latter had been mistyped as 3390. (Closes: #620126) Thanks to Stephen Powell for getting the kernel developers to fix this in the kernel back in 2011. * Allow to specify DASD_USE_DIAG=(0/1) and DASD_READONLY=(0/1) in DASD configuration files. (Closes: #620205) * Fix a few syntax disobediences. Thanks to Stephen Powell for the patch. (Closes: #795954) Checksums-Sha1: 867214867996e950a738b39eb20ebe34219857ec 1082 sysconfig_0.0.10+nmu2.dsc 4447fbe4d707b5bf6c1165cc55fc3d03db642466 8464 sysconfig_0.0.10+nmu2.tar.gz c981dbbb7076e3de49bffbe4ad61db551efada32 8136 sysconfig-hardware_0.0.10+nmu2_s390x.deb Checksums-Sha256: dcab3328987f39038565a1f17ab1899d3624b05d3a032857d377091a14695dc1 1082 sysconfig_0.0.10+nmu2.dsc 67f73955d4dbc89fc139028d0dd0a7a188a9728320d30df38cf508a8ed1ee6a6 8464 sysconfig_0.0.10+nmu2.tar.gz 6236a57d1823a529762ed40fa8f9d9d34b68a3d7e3ff408fd8c9c752412c182b 8136 sysconfig-hardware_0.0.10+nmu2_s390x.deb Files: 83b509ca194deba892e2a2321c65fd58 1082 admin optional sysconfig_0.0.10+nmu2.dsc 4c859dc01b3ce99a92c8684d829e052b 8464 admin optional sysconfig_0.0.10+nmu2.tar.gz 5371ef15e2c58ab7ea43233bccd84ed3 8136 admin standard sysconfig-hardware_0.0.10+nmu2_s390x.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJV7JCxAAoJEERuJUU10FbsX7oH/jGbooF6atvHUF1FzIPjQDcM tEn3IQGp2VFwInzveMMHnGdNbLt39fovFyNpKC6eW8ka2GJL3s+fwJ7pd8sJgf5t YgF0lR9mhvH108MDIGbSwhjS4tTeHxaewBmsaBKXMt3zFj2JtvYuqN5Fp4GG8rwT h1Gk23zR4iGltIzLD4TNblVWPovg6bxDpZ32yCKtOqR6reP0aozZ/8meeLuzB+fV 4NUc/5g4yk749W8tb2knUp75enex8dSMlVTFSdJtFrtRwLOi+4RMmylBApNxKvCU teCnQWDy07S6lvXrLmr/34AbqGkIr0F7v7tfKapYChyoFsIymul3fdBwJW9JJxA= =AmXi -----END PGP SIGNATURE-----
--- End Message ---
