![]() I would like to point out one issue I had with the OpenZFSonOSX1.2.0.dmg disk image. Let me start by describing my configuration. ![]() In this post, I’ll cover some of the issues encountered along the way. It is not part of any OpenZFS version yet, the next version of OpenZFS 2.1 will not incorporate this very important functionality, however, it will surely be incorporated in the next major version of OpenZFS, but it is still unknown when it will be, the most important thing is that it will end arriving, surely the next year 2022. I recently decided to try out the OpenZFS implementation of ZFS on my mac desktop and so far, I’m impressed. The negative part of this new functionality is that it will take time to arrive. We can only expand the number of disks within a RAIDz without changing the type of RAIDz. For example, we could expand a RAIDz1 of three disks into one of four disks, although what we can never do is change from a RAIDz1 to a RAIDz2, for example. ![]() Now the zfs command “zpool attach” will not only be able to add one more disk in a configured mirror, but also in existing RAIDz in a vdev. At a domestic and business level, as the number of disks in a vdev could not be increased, it was very necessary to do good planning and know in detail the future storage needs, because once it was done and configured we could not do anything else to be able expand a vdev, the only thing we could do is add an additional vdev.Ĭurrently in the typical RAID that we can use with the EXT4 file system, we can expand and even change the type of RAID in certain cases, with the aim of expanding storage or data integrity, however, with RAIDz this does not it has been possible from the beginning, until now. Now this has changed, and we can increase the number of disks in a vdev configured as RAIDz. Until now, if we wanted to expand the storage of a zpool, it was enough to add an additional disk if we had it configured as “Individual” or as “Mirror”, however, this was not possible in the RAIDz of the different levels. After updating macOS I vaguely recall reinstalling zfs for this version of macOS (and possibly uninstalling it first-fairly certain I followed the directions associated with the installer or in the wiki), and then later as zfs was updated. Most developers are only familiar with the integration process for their operating system of choice. Yes it is: I am using zfs, including after upgrading to High Sierra and after updating zfs a few times. For example OpenZFS on illumos must follow the illumos integration process because it is part of the larger illumos operating system repository. A pool can contain several vdevs, it is not necessary that the size of the different vdevs be the same. Each implementation has its own process for integrating changes, some of which cannot be changed. We must remember that the ZFS structure is organized in zpool which is in the upper part, just below we will find the vdev that can be configured in “Individual”, “Mirror”, and the different levels RAIDz1, RAIDz2 and RAIDz3, depending on the level of security to the integrity of the data you want to provide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |