Did you do a "vgreduce VGname /dev/dasd*" If you missed that step, you can probably fix it with "vgreduce --removemissing VGname"
You'll want to get rid of them from linux too if you haven't already. "dasd_configure 0.0.xxxx 0 0 " should do it. -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Jorge Fábregas Sent: Tuesday, May 30, 2017 11:47 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Remove DASD device Hi, We have a situation with two SLES11 servers. We had to migrate the underlying PVs used for the swap logical volume (we used pvmove to move from DASD to FCP LUNs) and then we removed the DASD PVs from the volume group (followed by pvremove on them to wipe LVM metadata). After that I called my z/VM admin and asked him to remove the corresponding DASD devices. He did but I still have the device files associated with them (/dev/dasd*)... The problem is that, whenever I type any LVM command, the command gets stucked (doesn't return the prompt). I guess vgscan is getting stuck reading these non existing DASD device files. I could fix this by excluding these devices (LVM filter) or by rebooting but I'm wondering if there's a a way to remove these DASD device files dynamically? For regualr SCSI devices one usually performs: echo offline > /sys/block/$DISK/device/state echo 1 > /sys/block/$DISK/device/delete ...but I don't see "state" nor "delete" for /sys/block/dasd*/device/* and Google didn't help that much. Thanks in advance! Regards, Jorge ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
