Comment 28 for bug 2009141

Revision history for this message
bugproxy (bugproxy) wrote : host_installer_shell_cmds_04062023_1.txt

------- Comment on attachment From <email address hidden> 2023-04-06 17:43 EDT-------

Reference attached file host_installer_shell_cmds_04062023_1.txt on DMP details, from the shell for command executed in shell

Note after chzdev --enable, Quantity 1969 files generated in /var/log/crash filling up /
i.e.
ls -l /var/crash
chzdev --enable 0.0.100d
lszdev
ls -l | grep unknown | wc -l
1969

i.e.
  45590 Apr 6 12:17 1680808641.142762184.unknown.crash.gz
     90 Apr 6 12:17 1680808641.142762184.unknown.meta.gz
  45751 Apr 6 12:17 1680808641.190968275.unknown.crash.gz
     77 Apr 6 12:17 1680808641.190968275.unknown.meta.gz
.
.
.
 142575 Apr 6 12:18 1680808725.929860353.unknown.crash.gz
     77 Apr 6 12:18 1680808725.929860353.unknown.meta.gz
 162995 Apr 6 12:18 1680808726.069142342.unknown.crash.gz
     77 Apr 6 12:18 1680808726.069142342.unknown.meta.gz
 141831 Apr 6 12:18 1680808726.164782763.unknown.crash.gz
     77 Apr 6 12:18 1680808726.164782763.unknown.meta.gz

Includes
lszdev --auto-conf
multipath -l
lszfcp
fdisk -l /dev/mapper/xxxxx
ls -l /var/crash | wc -l <=============== Quantity 1969 files generated filling up /

root@ubuntu-server:~# df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 3294672 305604 2989068 10% /run
/dev/loop0 iso9660 1149188 1149188 0 100% /cdrom
/cow overlay 16473348 16473348 0 100% /
overlay overlay 292992 292992 0 100% /media/filesystem
tmpfs tmpfs 16473348 0 16473348 0% /dev/shm
tmpfs tmpfs 5120 0 5120 0% /run/lock
tmpfs tmpfs 16473348 0 16473348 0% /tmp
tmpfs tmpfs 3294668 4 3294664 1% /run/user/1000
overlay overlay 292992 292992 0 100% /tmp/tmpcsrrjbgt/root.dir

In response to
> try manually wiping out the disk that have old LVM

Some of the luns are older OS Boot luns similar to lun mpathb (Boot lun for ubuntu 20.04).

Wiping these luns would not be an option as they are needed for ongoing tests and/or support

Will use a work-around to unmap such luns from the host during a new OS install so a new lun [i.e. for 20.04.2) can be installed

Another OS Boot lun is 20.04.1 on zfcp-host 120d/130d [not enabled for latest run]

Boot lun for ubuntu 20.04
lun mpathb (360050762198c1fc2180000000b000132) = (Boot lun for ubuntu 20.04)

mpathb (360050762198c1fc2180000000b000132) dm-1 IBM,FlashSystem-9840
size=50G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
  |- 0:0:1:0 sdc 8:32 active undef running
  `- 0:0:4:0 sdi 8:128 active undef running

fdisk -l /dev/mapper/mpathb
Disk /dev/mapper/mpathb: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: D3739269-492B-463E-927C-5441496FB8F3

Device Start End Sectors Size Type
/dev/mapper/mpathb-part1 2048 2099199 2097152 1G Linux filesystem
/dev/mapper/mpathb-part2 2099200 104855551 102756352 49G Linux filesystem