Nowadays virtual environment are very common, thus a hot increase of an existing drive into a virtual machine is a very common operation (roughly equivalent to a LUN expansion in SAN).
When you expand a zpool device, the new size won’t be immediately available to zfs, but you can easily request an expand with the following:
Here’s the procedure for adding Oracle 12c DBMS as SMF service in Solaris 11.1, based on this guide. The version provided here is slightly modified for the sake of simplicity as It needs only the oracle.xml to run (no additional scripts or configuration are required).
The procedure should work even with previous versions of Oracle DBMS and Solaris 11/10 (untested).
Some time ago I’ve built some code to declare Finite State Machines in Java in an annotated fashion so you wouldn’t have to bother yourself with state handling. Since it turned out that the code has been useful in more than a couple occasions, I’ve decided to share it.
JSM comes as a tiny jar with an easy to use interface.
– More to come here! –
After putting your precious data into your preferred database (Oracle or MySQL if you’re here) your next worry should be how to back them up. Here Bacula comes to help as a valid opensource network enterprise backup system – but how to get it working with your database?
In this post you’ll find some scripts which I developed to integrate Oracle or MySQL seamlessly with Bacula, allowing it to:
- Do (hot) full backup of the database
- Do (hot) incremental backup (also known as incremental differential backup)
- Do (hot) differential backup (also known as incremental cumulative backup)
VMware ESXi 5 is not able to handle multi-lun devices by default, so many SCSI autoloaders are not supported as-is (as HP StorageWorks LTOs), showing only the tape drive or media changer but not both:
While executing proguard (via maven2) on MacOSX Snow Leopard, I’ve got the following error:
[proguard] Error: Can't read [/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/rt.jar] (No such file or directory)
Similarly, you can also get the following error:
[proguard] Error: Can't read [/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jsse.jar] (No such file or directory)
Lately I wanted to bring the advantages of ZFS (on Solaris 11 Express) to a Linux box using iSCSI. After following the Oracle guide, I’ve noticed an unexpected behaviour when discovering the iSCSI targets (from a CentOS host):
[root@zimbra ~]# iscsiadm -m discovery -t sendtargets -p 192.168.64.10 192.168.64.10:3260,1 iqn.2011-01.org.cyberz:storage:mail 192.168.64.106:3260,1 iqn.2011-01.org.cyberz:storage:mail ... [root@zimbra ~]#
That is, the iSCSI target was bound to all the avaible interfaces (including ip addresses of zones).
TP-Link TL-WR743ND is the PoE brother of the common TL-WR741ND wireless router which is supported flawlessly by openwrt. Since I’ve got one WR743ND, I wanted to convert it into a useful OpenWRT router but I figured out that, unfortunately, the WR743ND is not supported by OpenWRT (at least officially). Given the similarity to the supported WR741ND, I’ve decided to hack it a bit to get it work with OpenWRT.
CadSoft’s Eagle (a well known CAD tool for designing PCBs) is not compatible as-is with Linux 64 bit. In my case, after a fresh Fedora 14 install, I was getting this error:
# sh eagle-lin-5.10.0.run
eagle-lin-5.10.0.run: /tmp/eagle-setup.3778/eagle-5.10.0/bin/eagle: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
To get the thing done it’s enough to install the proper 32 bit libraries. On Fedora use yum to update the openssl package and then install the needed packages:
# yum update openssl
# yum install glibc.i686 libXrender.i686 libXrandr.i686 libXcursor.i686 freetype.i686 fontconfig.i686 libXi.i686 libpng.i686 openssl.i686 crypto.i686 libjpeg-turbo.i686 libstdc++.i686
Eagle is compiled with openssl 0.9.8, Fedora 14 ships with openssl 1.0, so we need to cheat a bit with symlinks:
# ln -s /usr/lib/libssl.so.10 /usr/lib/libssl.so.0.9.8
# ln -s /lib/libcrypto.so.10 /lib/libcrypto.so.0.9.8
Now your system is ready to run the Eagle installer.
Today I’ve discovered that the very common Symbios 22801 (aka Symbios Logic 53c875) SCSI controller is (unexpectedly) failing to be recognized by Solaris 10 on x64 hardware. In fact I was in the middle of the upgrade of my home backup infrastructure from an old DLT 20/40 to a newer DLT 40/80 to be connected to a Symbios card inside my Solaris box. Unfortunately after the reboot, the new card was unseen.