Quelle: zfs-auto-snapshot vs sanoid: which one is better? : zfs
Und wieder eine interessante Frage in Verbindung mit sanoid.
Es ist wohl Zeit, endlich auch mal einen genaueren Blick darauf zu werfen.
Was ist eigentlich DogeOS?
In Anbetracht der ungewissen Zukunft von OmniOS, ist DogeOS vielleicht eine Option zum testen.
DogeOS is a distribution based on SmartOS and FIFO project. It is made to be the ultimate cloud OS for data center.
- All industry proven features of SmartOS: ZFS, Dtrace, KVM, Zones and Crossbow.
- Ready-to-use management console from FIFO.
- Nearly 100% resource utilization of hardware.
- No installation time for Resource Node (a.k.a chunter node).
- Guided, fast (< 10min) provision of the first FiFo (management) zone, and works even without Internet access.
DogeOS is, as similar to Project FiFo and SmartOS, licensed under CDDL. It is free to use.
For that we need to edit the file /etc/inet/hosts. Now this file has entry in the following format:So to change the domain name, you need to give this file a write permission and then go on to change the second word to any FQDN eg mydomain.com Save the file and reboot, the warning should no longer appear.To change permission: chmod u+w hosts
Quelle: Don’t let „Your unqualified host name“ to get on your nerves (Sunny Affairs)
Wie wird man diese Meldung: „Your unqualified host name“ wieder los? A & O ist ein sinnvoller /etc/inet/hosts Eintrag.
The Future of OmniOS
Quelle: [OmniOS-discuss] The Future of OmniOS
Was wird die Zukunft von OmniOS bringen? Offensichtlich wird es für OmniOD kritisch. Nexenta Stor und viele andere Firmen setzen auf auf Illumos also wird es mit ZFS Storage Lösungen weiter gehen.
Sollte man vieleicht auf SmartOS oder Nexenta Community gehen? Oder gar das Orginal, Solaris pur? – stay tuned 😉
What is Syncoid and Openoid?
Policy-driven snapshot management and replication tools. Currently using ZFS for underlying next-gen storage, with explicit plans to support btrfs when btrfs becomes more reliable. Primarily intended for Linux, but BSD use is supported and reasonably frequently tested. http://www.openoid.net/products/
Syncoid works with OmniOS and could by an alternativ to nappit autosync jobs and rsync.
I prefere nappit driven zfs replication and backup jobs, but syncoid seams be worth the test.
Wie lange läuft ein ZFS Storagesystem? Hier ein Livesystem;
user@hostname> uname -a
SunOS hostname 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-2
user@hostname> uptime
1:10pm up 5241 day(s), 3:54, 1 user, load average: 0.01, 0.01, 0.01
user@hostname> psrinfo -v
Status of processor 0 as of: 09/16/16 13:11:49
Processor has been on-line since 05/12/02 09:15:42.
The sparcv9 processor operates at 200 MHz,
and has a sparcv9 floating point processor.
Status of processor 1 as of: 09/16/16 13:11:49
Processor has been on-line since 05/12/02 09:15:47.
The sparcv9 processor operates at 200 MHz,
and has a sparcv9 floating point processor.
user@hostname> prtconf -vp | grep Mem
Memory size: 512 MegabytesDank an reddit: https://www.reddit.com/r/zfs/
Die vom BDÜ herausgegebene Zeitschrift „MDÜ – Fachzeitschrift für Dolmetscher und Übersetzer“ ist die auflagenstärkste Fachzeitschrift für Dolmetscher und Übersetzer im deutschsprachigen Raum (Auflage zurzeit ca. 8.500 Exemplare). Das MDÜ berichtet praxisnah über Arbeitswerkzeuge wie Translation-Memory-Systeme, Terminologieverwaltungsprogramme und Wörterbücher. Interviews und Hintergrundberichte zu wissenschaftlichen Erkenntnissen, neuen Gesetzen und Vorschriften bringen Sie beruflich auf den neuesten Stand.
In der Dezember Ausgabe haben wir eine Anzeige zu dem Thema Storage und Projetex gestartet.
Hier kann man die Digitale Version der Zeitschrift einsehen: http://www.bdue-fachverlag.de/fachverlag/detail_fachzeitschrift
Why are deletions slow?
- Deleting a file requires a several steps. The file metadata must be marked as ‚deleted‘, and eventually it must be reclaimed so the space can be reused. ZFS is a ‚log structured filesystem‘ which performs best if you only ever create things, never delete them. The log structure means that if you delete something, there’s a gap in the log and so other data must be rearranged (defragmented) to fill the gap. This is invisible to the user but generally slow.
- The changes must be made in such a way that if power were to fail partway through, the filesystem remains consistent. Often, this means waiting until the disk confirms that data really is on the media; for an SSD, that can take a long time (hundreds of milliseconds). The net effect of this is that there is a lot more bookkeeping (i.e. disk I/O operations).
- All of the changes are small. Instead of reading, writing and erasing whole flash blocks (or cylinders for a magnetic disk) you need to modify a little bit of one. To do this, the hardware must read in a whole block or cylinder, modify it in memory, then write it out to the media again. This takes a long time.
What can be done?
zfs create -o compression=on -o exec=on -o setuid=off zroot/tmp ; chmod 1777 /zroot/tmp ; zfs set mountpoint=/tmp zroot/tmp copy to /zroot/tmp zfs delete zroot/tmp
source: http://serverfault.com/questions/801074/delete-10m-files-from-zfs-effectively
ZFS send & receive is a great feature and a good solution for remote backup. How to receive and then(!) send zfs snapshots?
Here is my codesnippet;
root@local:~# nc remote.dyndns.org 22553 | zfs receive -vd vol1 root@remoteserver:~# zfs send vol2/services/datastore_l@1 | nc -l -p 22553
works fine with OmniOS and Openindiana;