Question about vinum and contents of /dev/vinum

[Greg 'groggy' Lehey]

On Tuesday,  1 April 2003 at 16:16:38 -0800, John Fox wrote:
> 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?

In general, never copy device nodes.  In this particular case it would
be particularly bad, but Vinum always recreates them when it starts,
even if they were there first (they could be wrong).

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20030402/63194b36/attachment.bin