Strange thing is that they are all online and the file systems are working.

cdzea00a0149:~ # lsdasd
Bus-ID     Status      Name      Device  Type  BlkSz  Size      Blocks
==============================================================================
0.0.0101   active      dasda     94:0    ECKD  4096   703MB     180000
0.0.ff02   active      dasdb     94:4    FBA   512    976MB     2000000
0.0.ff00   active      dasdc     94:8    FBA   512    244MB     500000
0.0.ff01   active      dasdd     94:12   FBA   512    488MB     1000000
0.0.ff03   active      dasde     94:16   FBA   512    1953MB    4000000
0.0.0102   active      dasdf     94:20   ECKD  4096   7042MB    1802880
0.0.0103   active      dasdg     94:24   ECKD  4096   7042MB    1802880
0.0.0104   active      dasdh     94:28   ECKD  4096   7042MB    1802880
0.0.8000   active      dasdi     94:32   ECKD  4096   2347MB    600840
0.0.0191   active      dasdj     94:36   ECKD  4096   0MB       180
0.0.8001   active      dasdk     94:40   ECKD  4096   23033MB   5896620
0.0.8002   active      dasdl     94:44   ECKD  4096   23033MB   5896620
0.0.8003   active      dasdm     94:48   ECKD  4096   23033MB   5896620
0.0.8004   active      dasdn     94:52   ECKD  4096   23033MB   5896620
0.0.8005   active      dasdo     94:56   ECKD  4096   23033MB   5896620

cdzea00a0149:~ # pvs
  WARNING: Device for PV EMyoZ4-Vo0Y-xfl7-lon0-Mm9q-KJYO-HrwCZh not found or 
rejected by a filter.
  WARNING: Device for PV 9GiuC0-forO-pi2F-djcO-lKiT-S0e4-bCMz1Y not found or 
rejected by a filter.
  WARNING: Device for PV Ab8N3O-yIoE-0jkd-i8DT-gomU-3w0p-LCeppl not found or 
rejected by a filter.
  WARNING: Device for PV tgcpJQ-3iqV-UAWl-MOlX-Sk2o-p0nU-TH0fAL not found or 
rejected by a filter.
  WARNING: Device for PV o9pAHz-lwkI-zTXv-UBjP-WhTs-5bDK-9QUZSC not found or 
rejected by a filter.
  PV             VG     Fmt  Attr PSize  PFree
  /dev/dasdf1    system lvm2 a--   6.88g 396.00m
  /dev/dasdg1    system lvm2 a--   6.88g      0
  /dev/dasdh1    system lvm2 a--   6.88g 768.00m
  /dev/dasdi1    app    lvm2 a--   2.29g      0
  unknown device app    lvm2 a-m  22.49g      0
  unknown device app    lvm2 a-m  22.49g   1.98g
  unknown device app    lvm2 a-m  22.49g      0
  unknown device app    lvm2 a-m  22.49g   2.27g
  unknown device app    lvm2 a-m  22.49g   1.49g

cdzea00a0149:~ # df -h
Filesystem                Size  Used Avail Use% Mounted on
devtmpfs                  3.4G  8.0K  3.4G   1% /dev
tmpfs                     3.4G  4.0K  3.4G   1% /dev/shm
tmpfs                     3.4G  1.9M  3.4G   1% /run
tmpfs                     3.4G     0  3.4G   0% /sys/fs/cgroup
/dev/dasda1               676M  300M  342M  47% /
/dev/mapper/system-usr    3.9G  1.8G  1.9G  50% /usr
/dev/mapper/app-app        40G   33M   40G   1% /app
/dev/mapper/app-apps       45G   40M   45G   1% /apps
/dev/mapper/app-udeploy   2.0G  113M  1.9G   6% /apps/udeploy
/dev/mapper/app-corp      9.0G   33M  9.0G   1% /apps/corp
/dev/mapper/system-home   2.9G  5.0M  2.8G   1% /home
/dev/mapper/system-opt    2.9G  2.4G  388M  87% /opt
/dev/mapper/system-tmp    3.9G   35M  3.6G   1% /tmp
/dev/mapper/system-var    4.8G  723M  3.9G  16% /var
/dev/mapper/app-wsserver   12G  3.5G  8.6G  29% /apps/wsserver
/dev/mapper/system-boks   469M  167M  277M  38% /opt/boksm
/dev/mapper/app-cdunix   1014M  187M  828M  19% /opt/cdunix
tmpfs                     694M     0  694M   0% /run/user/8888
tmpfs                     694M     0  694M   0% /run/user/0
tmpfs                     694M     0  694M   0% /run/user/262444

It seems to be the 8001-8005 disks that it is confused about.  The kernel 
messages complained about every one of the disks.
 
/apps/corp should be on one of those

cdzea00a0149:~ # lvdisplay  /dev/app/corp -m
  WARNING: Device for PV EMyoZ4-Vo0Y-xfl7-lon0-Mm9q-KJYO-HrwCZh not found or 
rejected by a filter.
  WARNING: Device for PV 9GiuC0-forO-pi2F-djcO-lKiT-S0e4-bCMz1Y not found or 
rejected by a filter.
  WARNING: Device for PV Ab8N3O-yIoE-0jkd-i8DT-gomU-3w0p-LCeppl not found or 
rejected by a filter.
  WARNING: Device for PV tgcpJQ-3iqV-UAWl-MOlX-Sk2o-p0nU-TH0fAL not found or 
rejected by a filter.
  WARNING: Device for PV o9pAHz-lwkI-zTXv-UBjP-WhTs-5bDK-9QUZSC not found or 
rejected by a filter.
  --- Logical volume ---
  LV Path                /dev/app/corp
  LV Name                corp
  VG Name                app
  LV UUID                t8ZbPY-Bq9D-YFST-5M3R-6FvC-7B5M-bIL99W
  LV Write Access        read/write
  LV Creation host, time cdzea00a0149, 2017-04-23 16:55:43 -0500
  LV Status              available
  # open                 1
  LV Size                9.00 GiB
  Current LE             2304
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1024
  Block device           254:4

  --- Segments ---
  Logical extents 0 to 2303:
    Type                linear
    Physical volume     unknown device
    Physical extents    0 to 2303


cdzea00a0149:~ # touch /apps/corp/somedarnfile
cdzea00a0149:~ # ls -al /apps/corp/somedarnfile
-rw-r--r-- 1 root root 0 May  1 17:48 /apps/corp/somedarnfile


I'm sure it's a bug and I bet a reboot will fix it, but since this happened 
once before, I'd like to get to the bottom of it.



-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post
Sent: Monday, May 1, 2017 3:42 PM
To: [email protected]
Subject: Re: [LINUX-390] DASD driver errors - sles 12 sp2 current maintenance

>>> On 5/1/2017 at 05:11 PM, Marcy Cortes <[email protected]> 
>>> wrote: 
> Got weird warnings on LVM commands like these from the "pvs" command 
> on one server.
> 
> 
> WARNING: Device for PV EMyoZ4-Vo0Y-xfl7-lon0-Mm9q-KJYO-HrwCZh not 
> found or rejected by a filter.
> 
>   WARNING: Device for PV 9GiuC0-forO-pi2F-djcO-lKiT-S0e4-bCMz1Y not 
> found or rejected by a filter.
> 
>   WARNING: Device for PV Ab8N3O-yIoE-0jkd-i8DT-gomU-3w0p-LCeppl not 
> found or rejected by a filter.
> 
>   WARNING: Device for PV tgcpJQ-3iqV-UAWl-MOlX-Sk2o-p0nU-TH0fAL not 
> found or rejected by a filter.
> 
>   WARNING: Device for PV o9pAHz-lwkI-zTXv-UBjP-WhTs-5bDK-9QUZSC not 
> found or rejected by a filter.
> 
>   PV             VG     Fmt  Attr PSize  PFree
> 
>   /dev/dasdf1    system lvm2 a--   6.88g 396.00m
> 
>   /dev/dasdg1    system lvm2 a--   6.88g      0
> 
>   /dev/dasdh1    system lvm2 a--   6.88g 768.00m
> 
>   /dev/dasdi1    app    lvm2 a--   2.29g      0
> 
>   unknown device app    lvm2 a-m  22.49g      0
> 
>   unknown device app    lvm2 a-m  22.49g   1.98g
> 
>   unknown device app    lvm2 a-m  22.49g      0
> 
>   unknown device app    lvm2 a-m  22.49g   2.27g
> 
>   unknown device app    lvm2 a-m  22.49g   1.49g

It looks like you're missing 5 DASD volumes (or SCSI LUNs) for your app VG.  
Can you bring them online manually?  If so, then re-running grub2-install will 
likely fix this.

> Found this in the messages:
> 
> May 01 15:45:48 cdzea00a0149 kernel: dasd-eckd.b3193d: 0.0.0101: An 
> error occurred in the DASD device driver, reason=09 May 01 15:45:48 
> cdzea00a0149 kernel: dasd(eckd): I/O status report for device 
> 0.0.0101:
>                                      dasd(eckd): in req: 
> 000000007c001ed8
> CC:00 FC:04 AC:00 SC:17 DS:0E CS:00 RC:0
>                                      dasd(eckd): device 0.0.0101: 
> Failing
> CCW: 000000007c001fe8
>                                      dasd(eckd): Sense(hex)  0- 7: 80 
> 00 00
> 00 00 00 00 0f
>                                      dasd(eckd): Sense(hex)  8-15: ef 
> 05 00
> 00 00 00 00 00
>                                      dasd(eckd): Sense(hex) 16-23: 00 
> 00 00
> 00 3b 00 0f 00
>                                      dasd(eckd): Sense(hex) 24-31: 00 
> 00 60
> e0 00 00 00 00
>                                      dasd(eckd): 24 Byte: 0 MSG f, no 
> MSGb to SYSOP May 01 15:45:48 cdzea00a0149 kernel: dasd(eckd): Related 
> CP in req:
> 000000007c001ed8
>                                      dasd(eckd): CCW 000000007c001fe0: 
> 2760000C 7C001FF0 DAT:  18000000 486d1c00  00000000
>                                      dasd(eckd): CCW 000000007c001fe8: 
> 3E20401A 7BEC0000 DAT:  00000000 00000000  00000000 00000000  00000000
> 00000000  0000

I don't think that has anything to do with your problem.  From what I've seen, 
it comes out when the system encounters a non-Linux formatted volume.  I've 
tried to get someone to nail that down, but haven't been successful yet.


Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] 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/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] 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/

Reply via email to