Christian S.J. Peron d7af790b0d Currently, if the drives specified for volume creation are ... not active GEOM providers, it will result in a kernel panic. If the GEOM provider or disk goes away before the volume configuration data gets written to the disk, it will result in another kernel panic. o Make sure that the drives specified for volume creation are active GEOM providers. o When writing out volume configuration data to associated drives, make sure that the GEOM provider is active, otherwise continue to the next drive in the volume. Approved by: le, bmilekic (mentor)		2004-06-24 02:40:34 +00:00
..
geom_vinum_drive.c	No need to free the softc, because it wasn't allocated.	2004-06-22 18:13:43 +00:00
geom_vinum_init.c
geom_vinum_list.c
geom_vinum_plex.c	Add a function to clean up RAID5 packets and use it when I/O has	2004-06-23 23:52:55 +00:00
geom_vinum_raid5.c	Add a function to clean up RAID5 packets and use it when I/O has	2004-06-23 23:52:55 +00:00
geom_vinum_raid5.h	Add a function to clean up RAID5 packets and use it when I/O has	2004-06-23 23:52:55 +00:00
geom_vinum_rm.c
geom_vinum_share.c	Accept "sd len 0" and auto-size the subdisk correctly.	2004-06-23 21:15:55 +00:00
geom_vinum_share.h
geom_vinum_state.c
geom_vinum_subr.c	Handle dead disks in a somewhat sane way.	2004-06-16 14:41:04 +00:00
geom_vinum_var.h
geom_vinum_volume.c	Clean up allocated ressources when destroying the main vinum geom.	2004-06-18 19:53:33 +00:00
geom_vinum.c	Currently, if the drives specified for volume creation are	2004-06-24 02:40:34 +00:00
geom_vinum.h