Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Wow, thanks, that's amazing!A basic free reset functionality for everyone=modify from the last napp-it is not available in current release but will be back in the next default edition.
Does Napp-It supported NexentaStor4?
NexentaStor4 seems to be the only distribution that supports SMB2 though.
Also, would I be able to interchange pools between NexentaStor4 and Omni OS
?
Gotcha. Is there any disadvantage to just staying at ZFS v28 for maximum compatibility?
I'm trying to look at the ZFS feature flags, and I know I don't want compression (lz4_compress). Are there any other performance features that are missing from v28?
Is there any guide on configuring Solaris 11.2 sendmail to relay all mail through my ISP smtp server, including those mails generated by "svccfg setnotify problem-diagnosed"? I found some guides but having problems with authentication. Namely, FEATURE(`authinfo') in the config file triggers an error "authinfo.m4 not found", and AuthInfo line in the access file seems to be silently ignored (sendmail doesn't attempt to authenticate to the server). Also, how do I set the "from" address in these emails? I don't think my ISP will like mails originating from "noaccess@solaris" instead of my email address.
You have two options to expand ZFS pools
- add a new vdev. With newer 4k disks this will be a ashift=12 vdev
- replace all disks in a vdev with larger ones.
Last option is not possible as your vdevs are ashift=9 where you cannot replace them with newer 4k disks.
I would
- buy a new HBA and 7 larger disks (4-6 TB)
- build a new pool (Z2 with 6 disks)
- replicate data to the new pool
Now you can decide if you want to use your 2TB for backup
or add them to the new pool with forced ashift=12 to be capable
to replace them later with larger disks. The pool is unbalanced
what means that some data is only on one vdev (not as fast as
a balanced pool where all data are striped over all vdevs).
But this is mostly tolerable.
You can force ashift=12 either with a sd.conf modification or
when you include a 4k disk when you create a vdev (can replace it later)
The 7th new disk is your new hotspare and can be used to force ashift=12.
(I would try a force ashift=12 with a testpool prior adding it to your data pool
as you cannot remove when the force fails)
Eventually I would need to add another vdev of 4TB drives, so the question is what to do about the 2TB drives?
Do I use all of the 2TB drives or half of them in a vdev in the new pool?
You mentioned that it is unbalanced but tolerable? Can you elaborate?
What would you do?
In regards to you statement: The 7th new disk is your new hotspare and can be used to force ashift=12. (I would try a force ashift=12 with a testpool prior adding it to your data pool as you cannot remove when the force fails).
Is the 7th disk the 2TB drive or a new 4TB drive?
So... I just recreated my 18 TB RAID-Z2 array and 4 TB RAID10 arrays and made certain to create them using the 28v5 option in napp-it, but it looks like my file systems were created using file system version 6 so do I need to destroy and recreate my arrays again to use them in OmniOS?
I thought creating the pools using 28v5 would be enough and it took like around a week to copy the data back/forth to create the array. I didn't see any option in napp-it for v5 filesystem
OK. What's the migration route? I don't have anywhere else to store my data so would have to be in place.
Is that possible?
Gotcha. So do I have to recreate the entire pool or do I need to just recreate each file system? Either way I guess I have to transfer all my data again...Filesystem v.6 can be created on Oracle Solaris only and is not compatibel with OpenZFS. Between current OpenZFS versions, based on BSD, Illumos (Nexentastor4, OpenIndiana, OmniOS) or ZOL you do not need v.28 as they are all ZFS v.5000/ filesystem v.5 with feature flags. V28/5 is only needed to transfer pools from/to Oracle Solaris.
no problem from OI to OmniOS and vice versa
- export pool (optional, not needed)
- install OmniOS (or OI)
- import pool
OK - Can I create v5 filesystems on Solaris 11.2? (using the command-line)
If I could do that then I could just create/destroy each v6 file system without needing to destroy the entire pool.
What about migrating additional configurations? If you have permissions/etc setup in OI, is there an easy way to export through napp-it and import again in the new install?
Thanks! How can I verify the filesystem version from the command-line?
(That's what I don't really understand... I used napp-it on Solaris 11.2 and specified 28v5 when I created my new pools, but OmniOS complained about the filesystems being v6 instead of v5. Perhaps my problem is that the v5 was NOT inherited )
Thanks again. Sure enough, the pools are version 5, but the filesystems are v6. I should be OK just recreating each filesystem at v5 and copying the data, right? (so I can finally transfer to OmniOS)