We ran into various pvcreate failures and error messages were not clear. It would be nice if pvcreate gives more clear error messages when different kind of errors happen.

(In reply to Vivek Goyal from comment #1)
> We ran into various pvcreate failures and error messages were not clear. It
> would be nice if pvcreate gives more clear error messages when different
> kind of errors happen.

Vivek, the old bug is a lot to plow through.  Can you give a couple examples of what type of output you would like to see in response to certain errors?

(In reply to Jonathan Earl Brassow from comment #3)
> (In reply to Vivek Goyal from comment #1)
> > We ran into various pvcreate failures and error messages were not clear. It
> > would be nice if pvcreate gives more clear error messages when different
> > kind of errors happen.
> 
> Vivek, the old bug is a lot to plow through.  Can you give a couple examples
> of what type of output you would like to see in response to certain errors?

Jon,

pvcreate was giving us following message.

"Device /dev/xvdb1 not found (or ignored by filtering).". 

This is very generic and it would be nice if error was more specific.

For example, first breakdown could happen, whether device node is not present or whether it was ignored by filtering.

And even for filtering, it would be nice to know what does that mean. On what specific attribute, a device was filtered out.

closing for rhel7.  rhel8 will soon explain what filter rejected a device.