Wednesday, January 6, 2016


Making PyCharm 5.0.3 and CLion 1.2 run in 30-bit color mode

In 30-bit color mode on Linux, a fresh PyCharm 5.0.3 installation fails to start:

[06:33 PM][ehvatum@heavenly:~/pycharm-community-5.0.2/bin]> ./  
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
log4j:WARN No appenders could be found for logger (io.netty.util.internal.logging.InternalLoggerFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See for more info.
[    571]  ERROR - llij.ide.plugins.PluginManager - Unsupported bit depth: 30
sun.java2d.InvalidPipeException: Unsupported bit depth: 30
       at sun.java2d.x11.X11SurfaceData.getSurfaceType(
       at sun.java2d.x11.X11SurfaceData.getSurfaceType(
       at sun.awt.X11GraphicsConfig.getSurfaceType(
       at sun.java2d.xr.XRSurfaceData.createData(


Workaround: add -Dsun.java2d.opengl=true to PyCharm's java call.  This can be done by editing; relevant snippet:

# ---------------------------------------------------------------------
# Run the IDE.
# ---------------------------------------------------------------------
 "-Xbootclasspath/a:$IDE_HOME/lib/boot.jar" \
 -classpath "$CLASSPATH" \
 $VM_OPTIONS "-Djb.vmOptionsFile=$vm_options_file" \
 "-XX:ErrorFile=$HOME/java_error_in_PYCHARM_%p.log" \
 -Djb.restart.code=88 -Didea.paths.selector=PyCharm50 \
 -Dsun.java2d.opengl=true \
 com.intellij.idea.Main \

This trick also works for running CLion in 30-bit mode.  It presumably works with the other JetBrains IDEs, though I have not verified this.

Update: this workaround allows JetBrains IDEs to start in 30-bit mode, but they soon crash due to absolutely idiotic bugs in sun.java2d.opengl.  Oh well.  I guess I'll just delete all JetBrains stuff, never buy any of their products, and spread the word far and wide that they're basically retarded.  Until they fix this - which they never will, because the problem lies in the Oracle Java shit stack.  Nonetheless, the fault remains with JetBrains for going with Java.  Who could have possibly predicted that would be problematic?  Yeah, pretty much anybody.

Tuesday, January 5, 2016


Arch ZFS root with 4.1.15-1-lts kernel: boot fails with "ZFS: Unable to import root_pool", but "import root_pool" in rescue shell works!

On a particular system with heaps of drives and controllers (booting involves 10+ minutes of controller bioses loading, enumerating, scanning, installing, etc), with a ZFS root, the following Arch Linux issue has come, gone, and come again:
  • The initrd step of booting fails out to a rescue shell with the error, "ZFS: Unable to import pool root_pool".
  • In that rescue shell, running "zpool import root_pool" succeeds, leading me to wonder why the same thing had apparently just failed.
To get past this error, I've previously banged gongs, chanted in tongues, burned incense, sent postcards to Jesus, and things such as that.  However, the issue never quite went away.

Sigh.  What a pain.  And so, we arrive at our very last and final reserve strategy: using our brain.  Alright, brain.  Get to thinking.  In the mean time, I'm going to play some video games.

45 minutes later, our brain says:
"So, when you later try the thing that failed, the thing that failed then succeeds.  Maybe it just fails the first time because it's idiotic and can only ever work when retried, or perhaps the delay itself is the important part?  Who cares!  Just make it retry once or twice with increasing delays.  This is a good plan.  Do it.  No more thinking is required at this time.  Signing off."

Thanks, brain!  Let's try that.  We boot an Arch image with ZFS integrated from a thumb drive, then run "zpool import root_pool -R /mnt", and then we "arch-chroot /mnt".  There's this file, /usr/lib/initcpio/hooks/zfs.  We edit it (edited portion highlighted and italicized).


zfs_get_bootfs () {
    for zfs_dataset in $(/usr/bin/zpool list -H -o bootfs); do
        case ${zfs_dataset} in
            "" | "-")
                # skip this line/dataset
            "no pools available")
                return 1
                return 0
    return 1

zfs_mount_handler () {
    local node=$1
    if [ "$ZFS_DATASET" = "bootfs" ] ; then
        if ! zfs_get_bootfs ; then
            # Lets import everything and try again
            /usr/bin/zpool import $ZPOOL_IMPORT_FLAGS -N -a $ZPOOL_FORCE
            if ! zfs_get_bootfs ; then
                echo "ZFS: Cannot find bootfs."
                return 1

    local pool="${ZFS_DATASET%%/*}"
    local rwopt_exp=${rwopt:-ro}

    if ! "/usr/bin/zpool" list -H $pool 2>&1 > /dev/null ; then
        if [ "$rwopt_exp" != "rw" ]; then
            msg "ZFS: Importing pool $pool readonly."
            ZPOOL_IMPORT_FLAGS="$ZPOOL_IMPORT_FLAGS -o readonly=on"
            msg "ZFS: Importing pool $pool."

        if ! "/usr/bin/zpool" import $ZPOOL_IMPORT_FLAGS -N $pool $ZPOOL_FORCE ; then
            echo "ZFS: Unable to import pool $pool.  Sleeping for 10 seconds and then tying again."
            sleep 10
            if ! "/usr/bin/zpool" import -d /dev -N $pool -f ; then
                echo "ZFS: Unable to import pool $pool.  Sleeping for 60 seconds and then trying yet again."
                sleep 60
                if ! "/usr/bin/zpool" import -d /dev -N $pool -f ; then
                    echo "ZFS: Unable to import pool $pool, even after waiting a good long time for devices to show up."
                    return 1

    local mountpoint=$("/usr/bin/zfs" get -H -o value mountpoint $ZFS_DATASET)
    if [ "$mountpoint" = "legacy" ] ; then
        mount -t zfs -o ${rwopt_exp} "$ZFS_DATASET" "$node"
        mount -o zfsutil,${rwopt_exp} -t zfs "$ZFS_DATASET" "$node"

run_hook() {
    # Force import the pools, useful if the pool has not properly been exported
    # using 'zpool export '
    [[ $zfs_force == 1 ]] && ZPOOL_FORCE='-f'
    [[ "$zfs_import_dir" != "" ]] && ZPOOL_IMPORT_FLAGS="$ZPOOL_IMPORT_FLAGS -d $zfs_import_dir"

    if [ "$root" = 'zfs' ]; then

    case $zfs in

    if [ ! -f "/etc/hostid" ] ; then
        echo "ZFS: No hostid found on kernel command line or /etc/hostid. ZFS pools may not import correctly."

    # Allow up to 10 seconds for zfs device to show up
    for i in 1 2 3 4 5 6 7 8 9 10; do
        [ -c "/dev/zfs" ] && break
        sleep 1

Next, we run "mkinitcpio -p linux-lts", exit the chroot, "zpool export root_pool", reboot, and we see that the first zpool import attempt still fails.  However, we are then into the code we added, which waits ten seconds and tries zpool importing again.  This second attempt succeeds.

In summary: most likely, the "waiting for uevents" step that precedes the first import attempt does not do quite enough waiting. Waiting more and retrying works. There is some possibility that the import just fails the first time and works the second, but the point remains that waiting more and retrying works, and that's what we do.


July 2009   August 2009   September 2009   October 2009   November 2009   December 2009   January 2010   September 2010   December 2010   January 2011   February 2011   April 2011   June 2011   August 2011   February 2012   June 2012   July 2012   August 2012   October 2012   November 2012   January 2014   April 2014   June 2014   August 2014   September 2014   October 2014   January 2015   March 2015   April 2015   June 2015   November 2015   December 2015   January 2016   June 2016   August 2016   January 2017   March 2017  

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]