gmirror suprises

[Ferruccio Zamuner]

% gmirror label -v -b prefer sroot ad2s1a ad6s1a
% ls -l /dev/mirror/
total 0
crw-r-----  1 root  operator    0, 171  8 Ott 21:32 sroot
crw-r-----  1 root  operator    0, 172  8 Ott 21:32 sroota
crw-r-----  1 root  operator    0, 173  8 Ott 21:32 srootb
crw-r-----  1 root  operator    0, 174  8 Ott 21:32 srootc
crw-r-----  1 root  operator    0, 175  8 Ott 21:32 srootd
crw-r-----  1 root  operator    0, 176  8 Ott 21:32 sroote
crw-r-----  1 root  operator    0, 177  8 Ott 21:32 srootf
crw-r-----  1 root  operator    0, 178  8 Ott 21:32 srootg
crw-r-----  1 root  operator    0, 179  8 Ott 21:32 srooth
% newfs /dev/mirror/sroot
/dev/mirror/sroot: 600.0MB (1228796 sectors) block size 16384, fragment 
size 2048
        using 4 cylinder groups of 150.00MB, 9600 blks, 19200 inodes.
super-block backups (for fsck -b #) at:
 160, 307360, 614560, 921760
% mount /dev/mirror/sroot /mnt/root4
mount: /dev/mirror/sroot: No such file or directory
% mount /dev/mirror/sroota /mnt/root4
% mount
[..]
/dev/mirror/sroota on /mnt/root4 (ufs, local)

Why it creates sroota/b/c/d/e/f/g/h?

I've created more gmirror on some other partition of the same disks 
(ad2s1e, ad6s1d) without this strange behaviour.
Is there something that I've to know?


Bye,                   \fer