No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

FAQ- the disk information scanned by fdisk -1 is different from that by vxdisk list

Publication Date:  2012-10-16  |   Views:  231  |   Downloads:  0  |   Author:  SU1000864011  |   Document ID:  EKB1000017232


Issue Description

There are four disks scanned by fdisk -1, while there are five scanned by vxdisk list.

Alarm Information


Handling Process

Sdb is a virtual physical disk, run rm delete command by hand to delete it.
Suggestions and summary:

Root Cause

What vxdisk list sees is the DMP floor of VXVM sends inq command to the device, if the command is returned, the disks are in position. The other disk sdb scanned by vxdisk list is related to a real physical device sdb. The device cannot be seen in fdisk -1, but you can send inq command to it, and returned successfully. The kernel of the problem is you can send inq command to the disks which cannot scanned by fdisk -1. The scan results of vxdisk list and fdisk -1 are diffrents is lead by dmp of vxvm, and it is normal. But read and write command cannot be sent.