- Joined
- May 17, 2014
- Messages
- 3,611
This is somewhat off-topic, so moderators feel free to move it to the Off-topic forum.
From what I can tell, their are few limitations on pool names. Certain pool names are
forbidden, like "spare" and "mirror", etc... Solaris' default for bootable OS pools is
"rpool". Makes sense and has the word "pool" in it. Get's kinda confusing when you
try this command;
But, after a while you get used to that typo :). I have even considered making a soft-link
to "zpool", but since I would not beable to do that in our Solaris production servers, it's a
bit pointless. FreeNAS uses "freenas-boot" for the OS part, not "rpool". But, it's more
descriptive showing both OS type, FreeNAS and what it's used for, booting.
Spring of 2014 I started using ZFS on Linux, (or more appropriately, Linux root on ZFS).
For both my little media, and workstation, it made sense to have a separate root OS pool,
(so I could mirror), and other pool, (like for media). So, now comes the naming. I use Solaris
at work, so "rpool" for root OS. Media seemed obvious too, "mpool".
But, my desktop, (called "arwen", gee I wonder why?), I initially used "apool". A co-worker
who is a fan of Doctor Who, (I guess I am, just not a fanatic), said it should have been
"apond" instead "apool". So I renamed my "apool" to "amypond".
A gold star to the first person who correctly identifies why...
On a more serious note, users of FreeNAS should give thought, (perhaps less than 10
seconds), on pool names. A badly named pool can likely cause problems. For example,
naming a data pool "freenas-pool" might lead to typos, (even with a GUI), when mistaking
"freenas-boot" for your data pool.
Of course, going to extremes is a bit silly too;
myserver-data-pool
myserver-backup-pool
So, what is your most interesting ZFS Pool name? And why?
From what I can tell, their are few limitations on pool names. Certain pool names are
forbidden, like "spare" and "mirror", etc... Solaris' default for bootable OS pools is
"rpool". Makes sense and has the word "pool" in it. Get's kinda confusing when you
try this command;
Code:
rpool status rpool
But, after a while you get used to that typo :). I have even considered making a soft-link
to "zpool", but since I would not beable to do that in our Solaris production servers, it's a
bit pointless. FreeNAS uses "freenas-boot" for the OS part, not "rpool". But, it's more
descriptive showing both OS type, FreeNAS and what it's used for, booting.
Spring of 2014 I started using ZFS on Linux, (or more appropriately, Linux root on ZFS).
For both my little media, and workstation, it made sense to have a separate root OS pool,
(so I could mirror), and other pool, (like for media). So, now comes the naming. I use Solaris
at work, so "rpool" for root OS. Media seemed obvious too, "mpool".
But, my desktop, (called "arwen", gee I wonder why?), I initially used "apool". A co-worker
who is a fan of Doctor Who, (I guess I am, just not a fanatic), said it should have been
"apond" instead "apool". So I renamed my "apool" to "amypond".
A gold star to the first person who correctly identifies why...
On a more serious note, users of FreeNAS should give thought, (perhaps less than 10
seconds), on pool names. A badly named pool can likely cause problems. For example,
naming a data pool "freenas-pool" might lead to typos, (even with a GUI), when mistaking
"freenas-boot" for your data pool.
Of course, going to extremes is a bit silly too;
myserver-data-pool
myserver-backup-pool
So, what is your most interesting ZFS Pool name? And why?