Question about vinum and contents of /dev/vinum

[John Fox]

I am copying files over the network -- from a failing drive in production
box to a new drive in my workstation, with the intent of swapping these
drives.

I have been testing transfers with tar, and ran into some problems when
it (tar) hit the '/dev/vinum' hierarchy:

  tar: dev/vinum/plex/virtdisk_plex: minor number too large; not dumped
  tar: dev/vinum/sd/drive0: minor number too large; not dumped
  tar: dev/vinum/sd/drive1: minor number too large; not dumped
  tar: dev/vinum/vol/virtdisk.plex/virtdisk_plex: minor number too large; not dumped
  tar: dev/vinum/Control: minor number too large; not dumped
  tar: dev/vinum/control: minor number too large; not dumped
  tar: dev/vinum/controld: minor number too large; not dumped
  tar: dev/sa0.ctl: minor number too large; not dumped

My question is this: When vinum starts up and can't find some of these
device files, will it crash and burn, or will it simply create them?

Thanks in advance for any help,

 
John
+---------------------------------------------------------------------------+
| "I can't believe I'm back on Mars. Three times before this place almost   |
|  killed me. I swore I would never give it another chance to complete      |
|  the job. Humans got no business being here. No business at all."         |
|  -- Michael Garibaldi, _Babylon 5_, "The Exercise of Vital Powers         |
+---------------------------------------------------------------------------+
| John Fox <jjf at mind.net> | System Administrator | Internet Ventures Oregon |
+---------------------------------------------------------------------------+