amtriorix
Dabbler
- Joined
- Feb 12, 2021
- Messages
- 12
Hello,
I run ZFS since day one on FreeBSD and several boxes using ZFSguru.
Despite the fact ZFSguru is not updated for about a year, it still runs rock solid.
After the years and using in fact only zfs to protect against bitrot, I found it very easy to NOT use SMB or NFS,
but simply a ZFS VOL in a raidz2 using iscsi and only ONE server that uses the iscsi target. Sharing was done on the server, including backup
So the NAS was pretty simple, the only things I did need was tuning, zfs, iscsi, smart, zfs scrub and selfhealing and of course reports.
However I would like to have my backup also on the nas and seen the plugins of zfsgure were pretty outdated, I had a problem.
I also did want to have a deep file search and index system, so I was stuck.
Of course I could run them on the server, but I am stubborn.
Seen I use a heave backup plan, using duplicity (s3 cloud using asymmetric encryption), borgbackup
and some sync methods with rclone and s3ql (using big cache), I decided to give a try to freenas, oeps truenas.
It is a complete disaster at the point of setup. I really do expect better guys.
FreeBSD runs ZFS at root since years. I want to see on my disks
1) a zfs construction using GPTid or in case of linux UUID, seen the later for can swap labels if a disk is down, the first, performs it automagically but still I prefer ID
better safe then sorry, especially with ZFS
2) ZFS using whole disks
3) in case of partitions, proper alignment (4K, ashift, etc)
4) before install of any nas software, I want to see ZFS predefined profiles, from the equivalent of stripe, mirror, raidz1, raidz2, raidz3 and the possibility to map
L2ARC cache
5) i want to see before install an advanced section of zfs to set compression, etc etc
6) a section to tune freebsd sysctl
So I did install treuenas, selected 6 discs and without any further question, the software did start to create a MIRROR zfs pool in my 6 discs, where I did
wanted actually a raidz2...
So in terms of truenas, it should be really better.
Everything related to nfs, samba and all those services are 3th priority services.
The first priority is:
1) high configurable and tunable setup, like:
a) FreeBSD system
b) ZFS filesystem, also with profiles to create the right zfs system and ZVOL, also config options such as compression type, prefetch or not, etc.
c) network
d) logging (including external newsyslog)
e) signaling with SNMP
f) reporting with mailreports
g) temperature control
h) WoL and powermanagement
i) UPS and handling in case of power outage
j) smart harddisk
k) heartbeat
l) NTP client to have the proper time
m) scrub and repair options at the cli menu/repair mode
The second priority:
nice status screens and GUI
create the proper authentication
Third priority
select the used 'sharing services' with plugins such as NFS, SAMBA and ISCSI
(remember there is no need to have NFS and SAMBA if ISCSI is used only but protection should be in place with firewall and ONE connection only to the target)
Fourth priority
backup plugins
Fifth priority
search and indexing
Six priority
everything else in truenas
Sixth priority
mobile app.
I suggest to try to find old articles on the internet about ZFS and FreeBSD, especially related to alignment and ZFS on root and for sure GPTid/UUID/etc
but also to setup a test base, then power off harddisks in a raidz...config, powercut and see if everything boots up properly or could be repaired.
Sop this is a highly recommended layout of course open for debate. But anyway, if truenas has no configurable ZFS profiles before install
of the truenas, it is basically for me, useless until this is modified properly.
Seen FreeBSD is porting OpenZFS, maybe it is time to move all together to the linux base, seen many ports like s3ql are broken on BSD.
And I say this with pain in my heart.
I run ZFS since day one on FreeBSD and several boxes using ZFSguru.
Despite the fact ZFSguru is not updated for about a year, it still runs rock solid.
After the years and using in fact only zfs to protect against bitrot, I found it very easy to NOT use SMB or NFS,
but simply a ZFS VOL in a raidz2 using iscsi and only ONE server that uses the iscsi target. Sharing was done on the server, including backup
So the NAS was pretty simple, the only things I did need was tuning, zfs, iscsi, smart, zfs scrub and selfhealing and of course reports.
However I would like to have my backup also on the nas and seen the plugins of zfsgure were pretty outdated, I had a problem.
I also did want to have a deep file search and index system, so I was stuck.
Of course I could run them on the server, but I am stubborn.
Seen I use a heave backup plan, using duplicity (s3 cloud using asymmetric encryption), borgbackup
and some sync methods with rclone and s3ql (using big cache), I decided to give a try to freenas, oeps truenas.
It is a complete disaster at the point of setup. I really do expect better guys.
FreeBSD runs ZFS at root since years. I want to see on my disks
1) a zfs construction using GPTid or in case of linux UUID, seen the later for can swap labels if a disk is down, the first, performs it automagically but still I prefer ID
better safe then sorry, especially with ZFS
2) ZFS using whole disks
3) in case of partitions, proper alignment (4K, ashift, etc)
4) before install of any nas software, I want to see ZFS predefined profiles, from the equivalent of stripe, mirror, raidz1, raidz2, raidz3 and the possibility to map
L2ARC cache
5) i want to see before install an advanced section of zfs to set compression, etc etc
6) a section to tune freebsd sysctl
So I did install treuenas, selected 6 discs and without any further question, the software did start to create a MIRROR zfs pool in my 6 discs, where I did
wanted actually a raidz2...
So in terms of truenas, it should be really better.
Everything related to nfs, samba and all those services are 3th priority services.
The first priority is:
1) high configurable and tunable setup, like:
a) FreeBSD system
b) ZFS filesystem, also with profiles to create the right zfs system and ZVOL, also config options such as compression type, prefetch or not, etc.
c) network
d) logging (including external newsyslog)
e) signaling with SNMP
f) reporting with mailreports
g) temperature control
h) WoL and powermanagement
i) UPS and handling in case of power outage
j) smart harddisk
k) heartbeat
l) NTP client to have the proper time
m) scrub and repair options at the cli menu/repair mode
The second priority:
nice status screens and GUI
create the proper authentication
Third priority
select the used 'sharing services' with plugins such as NFS, SAMBA and ISCSI
(remember there is no need to have NFS and SAMBA if ISCSI is used only but protection should be in place with firewall and ONE connection only to the target)
Fourth priority
backup plugins
Fifth priority
search and indexing
Six priority
everything else in truenas
Sixth priority
mobile app.
I suggest to try to find old articles on the internet about ZFS and FreeBSD, especially related to alignment and ZFS on root and for sure GPTid/UUID/etc
but also to setup a test base, then power off harddisks in a raidz...config, powercut and see if everything boots up properly or could be repaired.
Sop this is a highly recommended layout of course open for debate. But anyway, if truenas has no configurable ZFS profiles before install
of the truenas, it is basically for me, useless until this is modified properly.
Seen FreeBSD is porting OpenZFS, maybe it is time to move all together to the linux base, seen many ports like s3ql are broken on BSD.
And I say this with pain in my heart.