LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   lsblk failed to read (https://www.linuxquestions.org/questions/linux-server-73/lsblk-failed-to-read-4175604822/)

hansaplazt 04-27-2017 08:47 PM

lsblk failed to read
 
While shutting down a server I get errors in the console regarding raid device md127. I only get these errors while shutting down. The server boots up normally without errors and /proc/mdstat shows only healthy arrays.

This is the error I'm getting while shutting down the server.
Code:

Stopping block device availabillity: Deactivating block devices:
  [UMOUNT]: unmounting storage_vg0-storage01 (dm-9) mounted on /STOR01... done
  [MD]: deactivating raid5 device md2... skipping
  [MD]: deactivating raid5 device md1... skipping
  [MD]: deactivating raid1 device md0... skipping
  [LVM]: deactivating Volume Group kvm_vg0... done
  [MD]: deactivating raid5 device md127... done
lsblk: /sys/dev/block/9:127: failed to read link: No such file or directory
lsblk: /dev/md127: failed to get sysfs name: No such file or directory
/sbin/blkdeactivate: line 195: SKIP_DEVICE_LIST: bad array subscript
  [MD]: deactivating raid5 device md127... done
  [LVM]: deactivating Volume Group storage_vg0... done

If the system is up the link exists.
Code:

# ls -l /sys/dev/block/9\:127/
total 0
-r--r--r-- 1 root root 4096 Apr 28 02:53 alignment_offset
lrwxrwxrwx 1 root root    0 Apr 28 02:53 bdi -> ../../bdi/9:127
-r--r--r-- 1 root root 4096 Apr 28 02:53 capability
-r--r--r-- 1 root root 4096 Apr 28 02:52 dev
-r--r--r-- 1 root root 4096 Apr 28 02:53 discard_alignment
-r--r--r-- 1 root root 4096 Apr 28 02:53 ext_range
drwxr-xr-x 2 root root    0 Apr 28 02:52 holders
-r--r--r-- 1 root root 4096 Apr 28 02:53 inflight
drwxr-xr-x 7 root root    0 Apr 28 02:52 md
drwxr-xr-x 2 root root    0 Apr 28 02:53 power
drwxr-xr-x 2 root root    0 Apr 28 02:52 queue
-r--r--r-- 1 root root 4096 Apr 28 02:52 range
-r--r--r-- 1 root root 4096 Apr 28 02:52 removable
-r--r--r-- 1 root root 4096 Apr 28 02:52 ro
-r--r--r-- 1 root root 4096 Apr 28 02:52 size
drwxr-xr-x 2 root root    0 Apr 28 02:52 slaves
-r--r--r-- 1 root root 4096 Apr 28 02:53 stat
lrwxrwxrwx 1 root root    0 Apr 28 02:52 subsystem -> ../../../../class/block
drwxr-xr-x 2 root root    0 Apr 28 02:53 trace
-rw-r--r-- 1 root root 4096 Apr 28 02:52 uevent

md127 contains only one LV (storage01) in a VG (storage_vg0)
Code:

# lvdisplay storage_vg0
  --- Logical volume ---
  LV Path                /dev/storage_vg0/storage01
  LV Name                storage01
  VG Name                storage_vg0
  LV UUID                ...
  LV Write Access        read/write
  LV Creation host, time alvname, 2013-11-25 17:17:35 +0100
  LV Status              available
  # open                1
  LV Size                1.35 TiB
  Current LE            352738
  Segments              1
  Allocation            inherit
  Read ahead sectors    auto
  - currently set to    6144
  Block device          253:0

I need a little help trouble shooting this error.
Thank you in advance,

Best Hansa

624867243@qq.com 04-27-2017 09:05 PM

what is your system?Centos os or redhat?

syg00 04-27-2017 09:43 PM

Looks like something it attempting to tear-down md127 twice - and once it's gone, the second iteration issues the messages. Personally I'd ignore it, but if you feel inclined go through the shutdown sequence scripts.
Quote:

Originally Posted by hansaplazt (Post 5703292)
Code:

  [MD]: deactivating raid5 device md127... done
lsblk: /sys/dev/block/9:127: failed to read link: No such file or directory
lsblk: /dev/md127: failed to get sysfs name: No such file or directory
/sbin/blkdeactivate: line 195: SKIP_DEVICE_LIST: bad array subscript
  [MD]: deactivating raid5 device md127... done
  [LVM]: deactivating Volume Group storage_vg0... done




All times are GMT -5. The time now is 03:38 PM.