Description of problem:
running

multipath -b2

instead of

multipath -v2

can cause serious issues, remapping the users multipath devices.  With the fix for 1039935, this shouldn't cause corruption for already in use devices, but it can cause issues for anything relying on the user_friendly_names to always refer to the same device (which is otherwise a valid thing to do). Making -b require an absolute path name shouldn't cause any upgrade issues.  Users should
not need to use the -b option during normal operation.

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.7-46.el5

How reproducible:
Always

Steps to Reproduce:
1. create multipath devices with user_friendly_names enabled
        you will likely need to hand edit the bindings file to make it more likely that the devices will later be assigned different names
2. run multipath -b2  (or -b <any_non-existing_file_name>)
3. notice that the devices have been remapped.

Actual Results:

devices change their user_friendly names

Expected Results:

devices retain their existing names, and the command returns an error.