|
Lines 2725-2731
a|A pool consists of one or more vdevs, which themselves are a single disk or a
Link Here
|
| 2725 |
==== |
2725 |
==== |
| 2726 |
Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable. |
2726 |
Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable. |
| 2727 |
Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev. |
2727 |
Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev. |
| 2728 |
Reliably determining the size of an unpartitioned disk at boot time is impossible and because there's no place to put in boot code. |
2728 |
Reliably determining the size of an unpartitioned disk at boot time is impossible and there's no place to put in boot code. |
| 2729 |
==== |
2729 |
==== |
| 2730 |
|
2730 |
|
| 2731 |
* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`. |
2731 |
* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`. |