• AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
• 3 GB Ram
• 3x WDC WD5000AADS-00S9B0 (500 GB) in SW Raid 5
• nVidia Corporation G98 [GeForce 8400 GS]
• Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (DVB-T Card)
• nVidia Corporation MCP61 High Definition Audio (snd-hda-intel)
• LITE-ON DVDRW LH-20A1P, ATAPI CD/DVD-ROM drive

Linux Boot Step by Step

To give you an idea how the boot-process works in Linux, here’s a little step by step overview about what happens when:

1. Boot-loader
2. Kernel
3. Init
4. Services

Before you start to tune the boot-time of your System you should set yourself some goals. Don’t set unrealistic goals. My goals are:

• Kernel max 3 seconds
• Init-Scripts max 7 seconds

(a bit later you will notice that i switch from sysvinit to runit – and thus the goals change to: one-time-scripts: max 3 seconds, rest max 4 seconds) – This way i should achieve a boot-time of 10 seconds.


Another note: I’ll write about the disk-throughput in my examples below, however i don’t think this is a helpful value as this might change from boot-to-boot.


Current – Sysvinit, default kernel

Alright, let’s take a look at the current boot time. As you can see in this graphic my current boot is 47 seconds. According to the graphic we have 9 seconds for the Kernel till init starts and 38 seconds till the system is “ready to use”. You can see easily that every service is started one-by-one so if you have 10 services, and each is taking 2 seconds, we’re talking about 2*10 seconds. Now take a look at the top of the graphic, you’ll see that the disk throughput (31 mb/s) is not very good and the system is more or less “bored” while booting (which simply means, the system could do a lot more in the same time)

This is a big problem with SysvInit – But gladly there are sysvinit replacements around. For example runit, upstart and systemd. I personally dislike systemd and upstart – Upstart because of its dependencies to python and dbus. Systemd because it seems to be really buggy at the moment and the on-demand feature is imho something which shouldn’t go into an init-system (and let’s be serious – re-inventing xinetd/inetd makes which sense?) plus the fact that systemd needs cgroupthingy and thus won’t run on non-linux-platforms.


sysvinit to runit – minimal migration

After switching sysvinit to runit, and doing minimal migration of the services (runit is sysv compatible – so i just wrote all the init scripts except for a few into /etc/runit/1) i got this graphic, on which you can see the boot-time is at 36 seconds (11 seconds won) and the throughput is at 38 MB/s (7 MB/s won). The kernel takes only 7 seconds anymore (without doing anything to it – so no idea why this happened).

runit – fully migrated

After migrating everything possible (talking about the services from sysvinit scripts to runit-run-scripts) i got a screen with a boot time of 27 seconds (won another 9 seconds) and a throughput of 91 MB/s (which is near to the limit of my hard discs and an improvement of another 53 MB/s). Kernel time is still around 7 seconds.

So – the only thing we did was: Replacing SysVinit with Runit and migrating all services. Just by doing so we boot in 27 seconds of 47 (20 seconds less), and got a throughput of 91 MB/s instead of 31 (60 MB/s more). Of course, thats not all, and i still didn’t reached the goal of a 10 seconds boot. It’s time to take a look at the kernel.


modifying the kernel – remove not needed stuff

In this graphic you will see that i have a boot-time of 23 seconds (we won around 4 seconds) and a throughput of 68 MB/s (we lost around 23 MB/s). All i did was removing not needed modules and not needed stuff from the default Lunar Linux kernel, enabling preempt (low latency desktop). The kernel-time went down from ca 7 seconds to 5 seconds – so we won 2 seconds. However, the goal was 3 seconds – So i still need to do something with the Kernel. The easiest thing to have the Kernel at a 3 seconds boot is to just make everything which is not needed for a boot modularized. For example your USB-mouse and keyboard, your CD-ROM drive, your DVB-t card and similar stuff. That stuff doesn’t need to be available while booting the kernel, so make it a module…

make everything not important modular

…and i get this screen – which shows 24 seconds boot time (so we lost 1 second) and a throughput of 56mb/s (lost 12 MB/s) – However: The kernel-time is only around 3,2 up to 3,3 seconds instead of 5 seconds – So I’d say first goal achieved – Kernel needs only around 3 seconds. I’m sure it’s possible to boot the kernel in 2 seconds – do dmesg | less and enable kernel time display so that you can see what is “hanging” where – you can tune the time then by making things modular or by disabling them.

modify init/run scripts

As you can see in the latest graphic the time from running rcS to start the services in parallel is about 13 seconds long. As you might remember the goal was to have the one-time-scripts done/started within 3 seconds. So we’ll tune this now by modifying rcS.

Due to these changes the boot-time goes down from 24 seconds to 17 seconds – so we made it take 7 seconds less. And only 7 seconds to our “goal”. The time of the one-time-scripts went down to ca 5 seconds. So we need to get 2 more seconds out here. This means hacking the udev and mount script. Remember, we went down from 47 to 17 seconds already – and we didn’t touch mount, udev, x11 – So you’re booting Linux with x11 plus networking in 17 seconds.

hacking the udev and mount init script

For the mount script, which takes about 5 seconds, do the following: comment wait_some everywhere (except for the function at the start). Then remove the 2.4 kernel compatibility stuff and finally comment out LVM stuff (if you dont need it – i don’t).

Wow – Booting in 15 seconds.


To be continued… :)

Other Links

• Lunar Linux
• Boot Linux faster

1. “dd if=/dev/zero of=/mnt/filename bs=100M count=100″ on Node1 on the Clusterfilesystem
2. The same on the other node (Node2), the times should be equal.
3. Two times (2x) the same on Node1, the time will break in
4. Now on both nodes at the same time – The time should be higher, the higher the worse.

So, i did this checks on the System i’ve setup with DRBD and OCFS2, here are the results:

Check 1

ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
1048576000 bytes (1.0 GB) copied, 88.1202 s, 11.9 MB/s
real    1m29.530s
user    0m0.000s
sys     0m3.496s

Check 2

ER-20026:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
1048576000 bytes (1.0 GB) copied, 84.3576 s, 12.4 MB/s
real    1m24.622s
user    0m0.000s
sys     0m5.408s

Check 3

ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10 &
[1] 5252
ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
1048576000 bytes (1.0 GB) copied, 84.1481 s, 12.5 MB/s
real    1m24.314s
user    0m0.000s
sys     0m2.964s
1048576000 bytes (1.0 GB) copied, 137.668 s, 7.6 MB/s
[1]+  Done                    time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
real    2m19.164s
user    0m0.000s
sys     0m5.364s

Check 4

Node 1:
    ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
    1048576000 bytes (1.0 GB) copied, 156.417 s, 6.7 MB/s
    real    2m36.583s
    user    0m0.004s
    sys     0m2.512s
Node 2:
    ER-20026:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=10
    1048576000 bytes (1.0 GB) copied, 173.982 s, 6.0 MB/s
    real    3m24.200s
    user    0m0.000s
    sys     0m3.372s

My friend was interested into the %CPU and %WAIT Data of the nodes during test 3 and 4, so i will redo the tests now. As you can see above, i used 1 GB instead of 10 GB. My next test will use 2 GB:

The Box(es)

• 2 GB Ram
• Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
• 160 GB Sata (Seagate Barracuda 7200.10 family, ST3160215AS)
• Debian Lenny

top - 22:54:22 up 1 day,  7:04,  1 user,  load average: 0.08, 0.15, 0.11
Cpu0  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu1  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

Check 1

dd:
    ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20
    2097152000 bytes (2.1 GB) copied, 187.962 s, 11.2 MB/s
    real    3m8.043s
    user    0m0.000s
    sys     0m9.937s
Top after 30 seconds:
    top - 22:56:31 up 1 day,  7:07,  1 user,  load average: 1.86, 0.63, 0.27
    Cpu0  :  0.0%us,  1.6%sy,  0.0%ni, 66.3%id, 32.1%wa,  0.0%hi,  0.0%si,  0.0%st
    Cpu1  :  0.0%us,  8.9%sy,  0.0%ni, 18.4%id, 66.6%wa,  1.3%hi,  4.7%si,  0.0%st

Check 2

dd:
    2097152000 bytes (2.1 GB) copied, 178.706 s, 11.7 MB/s
    real    2m59.232s
    user    0m0.000s
    sys     0m5.836s
Top after 30 seconds:
    ER-40021:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20
    top - 22:38:37 up 1 day,  7:10,  1 user,  load average: 1.97, 0.53, 0.31
    Cpu0  :  0.0%us,  4.0%sy,  0.0%ni, 30.2%id, 61.1%wa,  1.7%hi,  3.0%si,  0.0%st
    Cpu1  :  0.0%us,  9.3%sy,  0.0%ni,  9.6%id, 78.0%wa,  0.7%hi,  2.4%si,  0.0%st

Check 3

dd:
    ER-20026:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20 &
    ER-20026:/var/lib/mysql# time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20 &
    2097152000 bytes (2.1 GB) copied, 205.511 s, 10.2 MB/s
    real    3m25.861s
    user    0m0.000s
    sys     0m6.152s
    2097152000 bytes (2.1 GB) copied, 205.622 s, 10.2 MB/s
    real    3m25.692s
    user    0m0.000s
    sys     0m3.500s
    [1]-  Done                    time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20
    [2]+  Done                    time dd if=/dev/zero of=/var/lib/mysql/test bs=100M count=20
Top after 30 seconds:
    top - 22:44:15 up 1 day,  7:16,  1 user,  load average: 2.29, 1.41, 0.80
    Cpu0  :  0.0%us,  2.7%sy,  0.0%ni,  3.7%id, 89.0%wa,  0.7%hi,  4.0%si,  0.0%st
    Cpu1  :  0.0%us,  2.1%sy,  0.0%ni, 92.8%id,  0.4%wa,  0.8%hi,  3.8%si,  0.0%st

Check 4

Node1:
    dd:
        2097152000 bytes (2.1 GB) copied, 410.541 s, 5.1 MB/s
        real    6m50.703s
        user    0m0.008s
        sys     0m3.448s
    Top after 30 seconds:
        top - 23:15:07 up 1 day,  7:25,  1 user,  load average: 1.19, 0.40, 0.37
        Cpu0  :  0.0%us,  0.3%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.3%si,  0.0%st
        Cpu1  :  0.0%us, 12.9%sy,  0.0%ni, 79.6%id,  4.2%wa,  0.8%hi,  2.5%si,  0.0%st
Node2:
    dd:
        2097152000 bytes (2.1 GB) copied, 400.627 s, 5.2 MB/s
        real    6m40.983s
        user    0m0.000s
        sys     0m7.560s
    Top after 30 seconds:
        top - 22:53:29 up 1 day,  7:25,  1 user,  load average: 2.03, 1.42, 1.19
        Cpu0  :  0.0%us,  2.0%sy,  0.0%ni, 88.7%id,  6.0%wa,  0.3%hi,  3.0%si,  0.0%st
        Cpu1  :  0.0%us,  4.4%sy,  0.0%ni, 67.4%id, 25.8%wa,  0.3%hi,  2.0%si,  0.0%st

As you can see, the Wait is quite high, this might be due to too slow discs or most likely the network. Both boxes are connected with each other over a 100mbit/s NIC so the datatransfer between those boxes is limited to technically 12MB/s (practically 10MB/s). However, i’ve shown this data to my friend and his comments were:

What we can see here is a mixture of two concurrency problems. Firsthand, it’s hard disk internal concurrency, the write head has to jump back and forth to write the different positions, of course. It’s the usual IOPS problem of magnetic disks.

The other problem here is concurrency between the nodes, two in this case. Changing blocks within the same file in the same directory and changing blocks that may still be in the file system cache of the opposite node – all that is stuff the cluster file system has to manage. It has to provide integrity, but should avoid locks whenever possible.

Now about the numbers of the 2GB test series. Tests 1 and 2 are desired to find the absolute range of IO power we are talking about. Test 3 tells us, how much the disk-internal concurrency affects our result, and Test 4 is what we are looking for.

You can see, Test 1+2 are 11MB/s each, if started concurrently on one node, it’s still 10MB/s but with about 90% of IO wait of the CPU. The high wait rate of Test 3 means, that the media is about to go in a saturation state now, luckily Jean caught something near the break even point with his test.

In preparation for Test 4, this tells us: All degradation in speed we can see from now on, is made by the cluster FS, not by the disk. Despite we have much less IO speed in Test 4 (5 MB/s vs. 10MB/s in reference), there is much less WAIT% now. WAIT% is “waiting for IO” – unlocking mechanisms my OCFS2 via network are causing slight SYS% increase instead. One last point of interest is to look for the limitation now – the values don’t provide it.

My guess is Networking: Bandwidth, or more likely: Latency.

Thanks to Martin (usn) for his time :-)

ich hab von glako (danke!) nen’ acer aspire one bekommen, da habe ich mir jetzt erstmal Lunar Linux installiert, läuft ganz fein. Wobei ich anfangs schon etwas Probleme hatte bei der Installation. Aber das liegt eher daran das ich kein externes CD Rom bzw DVD Rom habe und somit leichte Probleme hatte irgendwas auf dem Teil zu installieren mangels Media. Wie auch immer. Rechts solltet ihr nen Screenshot sehen können.

Die Auflösung ist 1024x600px. Es läuft alles einwandfrei, bis auf die Grafikkarte. Manchmal wackelt das Bild, als ob es kurz nach rechts und links geht, als ob der Display sowas wie Autoadjustment macht. Wobei das wirklich nicht so häufig passiert, das passiert nur unter Last. Möglicherweise irgendwas, was ich falsch eingestellt habe, in der xorg.conf oder so.

Bin ich mir gerade nicht sicher. Mal sehen ich will demnächst mal sehen das ich Bluetooth einbaue, eine 1.8″ oder 2.5″ Festplatte, sowie die grünen Leds durch blaue austausche. Erstes sollte beides möglich sein, dafür habe ich schon Howtos gefunden. Bin etwas verwirrt was die SSD angeht – Dazu existiert ein Haufen an Informationen, Fakt ist einfach: Niemand kann sagen wann die SSD den Geist aufgibt, weil ich nicht einsehen kann (auch nicht mit smartctl) wieviele cycles die SSD schon hatte. Anders als Festplatten ist eine SSD limitiert – Hat eine SSD also maximal 100 000 write cycles – Hält Sie exakt 100 000 mal – beim 101 000 mal ist sie tot. Ganz einfach. Allerdings habe ich auch schon Hochrechnungen gesehen nach denen eine SSD 7-519 Jahre halten soll.. Also.. Nunja.

Whatever :-)

First of all i enabled quota support in the Kernel. Then i added “usrquota,grpquota” to the options in /etc/fstab. After that i created the files quota.user and quota.group on / (which is the device i’m trying to work with quota on) and rebooted (-o remount was not working). Now back online i issued “quotacheck -avug” to the box and got:

quotacheck: Your kernel probably supports journaled quota but you are not using it. Consider switching to journaled quota to avoid running quotacheck after an unclean shutdown.
quotacheck: WARNING - Quotafile //quota.user was probably truncated. Cannot save quota settings...
quotacheck: WARNING - Quotafile //quota.group was probably truncated. Cannot save quota settings...
quotacheck: Cannot remount filesystem mounted on / read-only so counted values might not be right.
Please stop all programs writing to filesystem or use -m flag to force checking.

Let’s start using google. The first thing is easily solvable.. instead of “usrquota” and “grpquota” use: usrjquota.. and grpjquota i guess. However, issueing “mount /dev/sda2 / -t ext3 -o remount,rw,usrjquota=aquota.user,jqfmt=vfsv0″ brings nothing. dmesg is showing:

EXT3-fs: old and new quota format mixing.

This isn’t as easy as i thought to be honest…Then finally i found a howto, explaining it quite right. You have to do it this way:

1. Add “usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0″ to the partition you wanna use. For example:

wdp@yulivee ~ $ cat /etc/fstab | grep quota
/dev/sda2       /       ext3    defaults,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 1
wdp@yulivee ~ $

2. create some files, change permissions and remount the disc

touch /aquota.user /aquota.group
chmod 600 /aquota.*
mount -o remount /

3. Last Step, run the commands quotacheck -avugm and quotaon -avug

root@yulivee /home/wdp # quotacheck -avugm
quotacheck: WARNING -  Quotafile //aquota.user was probably truncated. Cannot save quota settings...
quotacheck: WARNING -  Quotafile //aquota.group was probably truncated. Cannot save quota settings...
quotacheck: Scanning /dev/sda2 [/] done
quotacheck: Checked 99960 directories and 1613505 files
root@yulivee /home/wdp # quotaon -avug
/dev/sda2 [/]: group quotas turned on
/dev/sda2 [/]: user quotas turned on
root@yulivee /home/wdp #

Nice nice nice :-) Now i need to do the PHP Part, for that i’m adding now a testuser with quotas and checking the outputs of df and the quota tools. But first we’re coming to another problem. Adding quotas for the user quotatest:

root@yulivee /home/wdp # edquota quotatest
Disk quotas for user quotatest (uid 1003):
  Filesystem                   blocks       soft       hard     inodes     soft     hard
  /dev/sda2                        20          0          0          6        0        0

I want to set 200 MB Quota and have to deal with blocks and inodes – Funny, or? However – Inodes is the Amount of files. Blocks depends on the system. Means first of all we need to check the size of a block on / – This can be done this way:

root@yulivee /home/wdp # tune2fs -l /dev/sda2 | grep "Block size"
Block size:               4096
root@yulivee /home/wdp #

Normally, we would calculate the quota limit in bytes / blocksize, the blocksize on my box is 4096 but this was not working. I had to use /1024 instead of /4096 to have a limit of 200 MB. So it seems you can ignore the blocksize of the filesystem completly.

Now we need to calculate a bit:

# ( Quota Limit in MB * 1024 * 1024 ) / 1024 = Blocks
( 200 * 1024 * 1024 ) / 1024 = 204800
# or:
200 MB * 1024 * 1024 = 209715200 (Bytes)
209715200 (Bytes) / 1024 = 204800 (Blocks)
# or:
200 MB * 1024 = 204800 Blocks

Now we know, that 204800 Blocks on my disc (filesystem) are 200 MB. For 195 MB it’s 199680. Now in edquota define it this way:

root@yulivee /home/wdp # edquota quotatest
Disk quotas for user quotatest (uid 1003):
  Filesystem                   blocks       soft       hard     inodes     soft     hard
  /dev/sda2                        20            199680   204800          6        0        0

okay, su – quotatest, type in quota, you’ll something similar to:

quotatest@yulivee ~ $ quota
Disk quotas for user quotatest (uid 1003):
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
      /dev/sda2  20 199680  204800            6       0       0

Seems to work, let’s now create a big file using dd, just to test whether quota is working or not:

quotatest@yulivee ~ $ dd if=/dev/urandom of=test.datei bs=1048576 seek=1024
sda2: warning, user block quota exceeded.
sda2: write failed, user block limit reached.
dd: writing `test.datei': Disk quota exceeded
150+0 records in
149+0 records out
157126656 bytes (157 MB) copied, 30.6894 s, 5.1 MB/s
quotatest@yulivee ~ $ du -h
200M    .

As you can see it’s working. Let’s come to the PHP Part. First of all we need to check whether there are quotas for the user or not. If there are quotas we have to check them, if not we have to check on which disc/partition the user is and how much of it free is.

if the system has no quotas the command quota will return nothing. If the system has quotas but no quotas are set for the user the command quota returns “Disk quotas for user wdp (uid 1000): none” for example if your username is wdp. If the system got quotas and quotas are set it will return something like what i wrote prior (just scroll up).

<?php

        // This is just an example, there might be nicer solutions
        // it will "echo" the free "blocks" which is the same then
        // KB in my example here.
        $quota = `quota -w`;
        if(empty($quota))
        {
                $quotas = false;
        } else
        {
                if(substr_count($quota, " ") == 7)
                        $quotas = false;
                else
                        $quotas = true;
        }

        if($quotas == true)
        {

                $toreplace = array("\r", "\n", "\t");
                $line = str_replace($toreplace, ' ', $quota);
                $line = preg_replace('/\s+/s', " ", $line);
                $array = explode(" ", $line);
                $quotaCurrent = $array[17];
                $quotaSoft = $array[18];
                $quotaHard = $array[19];
                if(($quotaSoft > 0) && ($quotaSoft > $quotaCurrent))
                        $free = $quotaSoft - $quotaCurrent;
                else
                        $free = $quotaHard - $quotaCurrent;
                echo $free;

        } else
        {

                // We reached this part because it
                // seems there are no usable quotas
                // this is a fallback!

        }

?>

copyrights_licenses_and_cddl_illustrated

Anyway. I think the CDDL is much more useful.

Let’s try it out. I got the Source of it from their Website: http://sysweb.cs.toronto.edu/projects/7 and tried to compile it as explained. What “tried” mean? Well, it could well be that this isn’t working at all as i’m not using vmware, nor qemu nor xen. Anyway.. In the Host i get:

-------------------------------------------------------------------------------
              Building stub-daemon for SunOS (RELEASE)
-------------------------------------------------------------------------------
gmake[3]: Entering directory `/export/home/chani/vmgl.hg/cr/stub-daemon'
Compiling daemon.c
Linking stub-daemon for SunOS
Undefined			first referenced
 symbol  			    in file
bind                                ../dist/lib//libvmglstubdaemon.a(vmgl-stub-daemon.o)
accept                              ../dist/lib//libvmglstubdaemon.a(vmgl-stub-daemon.o)
listen                              ../dist/lib//libvmglstubdaemon.a(vmgl-stub-daemon.o)
socket                              ../dist/lib//libvmglstubdaemon.a(vmgl-stub-daemon.o)
ld: fatal: Symbol referencing errors. No output written to ../dist/bin//stub-daemon
collect2: ld returned 1 exit status
gmake[3]: *** [../dist/bin//stub-daemon] Error 1
gmake[3]: Leaving directory `/export/home/chani/vmgl.hg/cr/stub-daemon'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/export/home/chani/vmgl.hg/cr/stub-daemon'
make[1]: *** [stub-daemon.subdir] Error 2
make[1]: Leaving directory `/export/home/chani/vmgl.hg/cr'
find: cannot read dir /etc/sfw/openssl/private: Permission denied
find: cannot read dir /etc/inet/secret: Permission denied
find: cannot read dir /etc/flash/postcreation: Permission denied
find: cannot read dir /etc/flash/precreation: Permission denied
find: cannot read dir /etc/flash/preexit: Permission denied
find: cycle detected for /lib/32/
find: cycle detected for /lib/secure/32/
find: cycle detected for /usr/lib/link_audit/32/
find: cannot read dir /usr/lib/mozilla: Permission denied
find: cycle detected for /usr/lib/locale/en_US.UTF-8/LC_CTYPE/32/
find: cycle detected for /usr/lib/locale/en_US.UTF-8/LO_LTYPE/32/
find: cycle detected for /usr/lib/locale/en_US.UTF-8/32/
find: cycle detected for /usr/lib/32/
find: cycle detected for /usr/lib/secure/32/
find: cycle detected for /usr/lib/elfedit/32/
find: cycle detected for /usr/lib/lwp/32/
install: libarrayspu.so was not found anywhere!
find: cannot read dir /etc/sfw/openssl/private: Permission denied
find: cannot read dir /etc/inet/secret: Permission denied
find: cannot read dir /etc/flash/postcreation: Permission denied
find: cannot read dir /etc/flash/precreation: Permission denied
find: cannot read dir /etc/flash/preexit: Permission denied
find: cycle detected for /lib/32/
find: cycle detected for /lib/secure/32/
find: cycle detected for /usr/lib/link_audit/32/
find: cannot read dir /usr/lib/mozilla: Permission denied
find: cycle detected for /usr/lib/locale/en_US.UTF-8/LC_CTYPE/32/
find: cycle detected for /usr/lib/locale/en_US.UTF-8/LO_LTYPE/32/
find: cycle detected for /usr/lib/locale/en_US.UTF-8/32/
find: cycle detected for /usr/lib/32/
find: cycle detected for /usr/lib/secure/32/
find: cycle detected for /usr/lib/elfedit/32/
find: cycle detected for /usr/lib/lwp/32/
install: glstub was not found anywhere!
make: *** [all] Error 1
chani@yulivee:~/vmgl.hg$

And in the Lunar Zone:

root@lunar ~/vmgl.hg # make
install -d /root/vmgl.hg/dist/lib/
install -d /root/vmgl.hg/dist/bin/
(cd cr ; \
	    make ; \
	    install -s -m 0755 dist/lib/*.so /root/vmgl.hg/dist/lib/ ; \
	    install -s -m 0755 dist/bin/* /root/vmgl.hg/dist/bin/ ; \
	) || exit 1
make[1]: Entering directory `/root/vmgl.hg/cr'
/bin/sh: gmake: command not found
make[1]: *** [util.subdir] Error 127
make[1]: Leaving directory `/root/vmgl.hg/cr'
install: cannot stat `dist/lib/*.so': No such file or directory
install: cannot stat `dist/bin/*': No such file or directory
make: *** [all] Error 1
root@lunar ~/vmgl.hg #

That was a simply “make” in host and guest. As you can see.. it’s not easy to compile this Stuff. Anyway. I have no time to try fixing this issues yet. Probably next week.

By the way, just in case someone is interested, the background is a graphic from “The Forbidden Kingdom” a film with Jet Li and Jackie Chan. Nice Movie, i like it, though never seen Jet Li in such a funny “art” before :)

today i wanna have a short look at ZFS, everytime i look at ZFS news and videos i get more interested into this filesystem but i bet i’m not alone. My first try getting opensolaris working within qemu failed. So i’ll try for now zfs-fuse (the linux port over fuse) with a bit luck i can play arround with ZFS then.

By the way, as i’m using “files” instead of real devices i can’t say anything to the performance.

first i need to install fuse and scons

root@chani ~ # lin -cr fuse scons
...

then i need libaio. doesn’t seem to be in my distribution, so i googled for it and installed it manually.

after wget’ing the zfs-fuse bz2 i compiled it

root@chani /home/wdp/Desktop # tar -xjvf
zfs-fuse-0.5.0.tar.bz2
root@chani /home/wdp/Desktop # cd zfs-fuse-0.5.0
root@chani /home/wdp/Desktop/zfs-fuse-0.5.0 # cd src
root@chani /home/wdp/Desktop/zfs-fuse-0.5.0/src # scons
...
root@chani /home/wdp/Desktop/zfs-fuse-0.5.0/src # scons install

then i had to start zfs-fuse

root@chani ~ # zfs-fuse

and then i created the first pool

root@chani /home/wdp # zpool create zfsmagic
raidz2 /home/wdp/disk1_zfs \
         /home/wdp/disk2_zfs \
         /home/wdp/disk3_zfs \
         /home/wdp/disk4_zfs \
         /home/wdp/disk5_zfs \
         /home/wdp/disk6_zfs \
         /home/wdp/disk7_zfs \
         /home/wdp/disk8_zfs \
         /home/wdp/disk9_zfs \
         /home/wdp/disk10_zfs \
         /home/wdp/disk11_zfs \
         /home/wdp/disk12_zfs
root@chani /zfsmagic # df -hT | grep zfs
zfsmagic      fuse     30G   45K   30G   1% /zfsmagic

seems nice so far

root@chani /zfsmagic # zpool status
  pool: zfsmagic
 state: ONLINE
 scrub: none requested
config:

        NAME                      STATE     READ WRITE CKSUM
        zfsmagic                  ONLINE       0     0     0
          raidz2                  ONLINE       0     0     0
            /home/wdp/disk1_zfs   ONLINE       0     0     0
            /home/wdp/disk2_zfs   ONLINE       0     0     0
            /home/wdp/disk3_zfs   ONLINE       0     0     0
            /home/wdp/disk4_zfs   ONLINE       0     0     0
            /home/wdp/disk5_zfs   ONLINE       0     0     0
            /home/wdp/disk6_zfs   ONLINE       0     0     0
            /home/wdp/disk7_zfs   ONLINE       0     0     0
            /home/wdp/disk8_zfs   ONLINE       0     0     0
            /home/wdp/disk9_zfs   ONLINE       0     0     0
            /home/wdp/disk10_zfs  ONLINE       0     0     0
            /home/wdp/disk11_zfs  ONLINE       0     0     0
            /home/wdp/disk12_zfs  ONLINE       0     0     0

errors: No known data errors
root@chani /home/wdp # zpool list
NAME       SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
zfsmagic  35.8G  3.00G  32.7G     8%  ONLINE  -

okay. so far so good. let’s now copy over some files. cp not mv. we just use to check some things. I just copy over some music songs (7 GB) let’s check again how much space we use, using df and zpool list:

root@chani /home/wdp # zpool list
NAME       SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
zfsmagic  35.8G  9.07G  26.7G    25%  ONLINE  -

root@chani /home/wdp # df -hT | grep zfs
zfsmagic      fuse     30G  7.6G   22G  26% /zfsmagic

As you can see, some differences in displaying the amount of used data. though this shouldn’t be a problem.

Now let’s do a .. crashtest. I’m first running zpool scrub to to make sure that integrety is okay.. after it i’ll check for the biggest zfs device file and remove this one using mv. at the same time i’ll play a song from that disc. Let’s see whether it works or not.

root@chani ~ # zpool scrub zfsmagic
root@chani ~ # zpool status
  pool: zfsmagic
 state: ONLINE
 scrub: scrub in progress for 0h9m, 48.38% done, 0h10m to go
config:

        NAME                      STATE     READ WRITE CKSUM
        zfsmagic                  ONLINE       0     0     0
          raidz2                  ONLINE       0     0     0
            /home/wdp/disk1_zfs   ONLINE       0     0     0
            /home/wdp/disk2_zfs   ONLINE       0     0     0
            /home/wdp/disk3_zfs   ONLINE       0     0     0
            /home/wdp/disk4_zfs   ONLINE       0     0     0
            /home/wdp/disk5_zfs   ONLINE       0     0     0
            /home/wdp/disk6_zfs   ONLINE       0     0     0
            /home/wdp/disk7_zfs   ONLINE       0     0     0
            /home/wdp/disk8_zfs   ONLINE       0     0     0
            /home/wdp/disk9_zfs   ONLINE       0     0     0
            /home/wdp/disk10_zfs  ONLINE       0     0     0
            /home/wdp/disk11_zfs  ONLINE       0     0     0
            /home/wdp/disk12_zfs  ONLINE       0     0     0

errors: No known data errors

let’s wait 10 minutes… :)

root@chani /home/wdp # du -h disk*
784M    disk10_zfs
784M    disk11_zfs
784M    disk12_zfs
784M    disk1_zfs
784M    disk2_zfs
784M    disk3_zfs
784M    disk4_zfs
784M    disk5_zfs
784M    disk6_zfs
784M    disk7_zfs
784M    disk8_zfs
784M    disk9_zfs

okay.. that will not be very useful. i just remove 1 random file.

root@chani /home/wdp # mkdir zfs_old
root@chani /home/wdp # mv disk6_zfs zfs_old/
root@chani /home/wdp # zpool scrub zfsmagic

at the same time i play a song on a different console.

root@chani ~ # zpool status
  pool: zfsmagic
 state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
        the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://www.sun.com/msg/ZFS-8000-2Q
 scrub: scrub in progress for 0h0m, 0.00% done, 208h30m to go
config:

        NAME                      STATE     READ WRITE CKSUM
        zfsmagic                  DEGRADED     0     0     0
          raidz2                  DEGRADED     0     0     0
            /home/wdp/disk1_zfs   ONLINE       0     0     0
            /home/wdp/disk2_zfs   ONLINE       0     0     0
            /home/wdp/disk3_zfs   ONLINE       0     0     0
            /home/wdp/disk4_zfs   ONLINE       0     0     0
            /home/wdp/disk5_zfs   ONLINE       0     0     0
            /home/wdp/disk6_zfs   UNAVAIL      0     0     0  cannot open
            /home/wdp/disk7_zfs   ONLINE       0     0     0
            /home/wdp/disk8_zfs   ONLINE       0     0     0
            /home/wdp/disk9_zfs   ONLINE       0     0     0
            /home/wdp/disk10_zfs  ONLINE       0     0     0
            /home/wdp/disk11_zfs  ONLINE       0     0     0
            /home/wdp/disk12_zfs  ONLINE       0     0     0

errors: No known data errors

wow! okay.. let’s remove one more. by the way, song is still playing.

root@chani /home/wdp # mv disk4_zfs zfs_old/
root@chani /home/wdp # zpool scrub zfsmagic

wow! still working… let’s remove one more.

root@chani /home/wdp # mv disk12_zfs zfs_old/

crashed. :)

root@chani /home/wdp # zpool scrub zfsmagic
zfsfuse_ioctl_read_loop(): file descriptor closed
cannot scrub zfsmagic: I/O error
root@chani /home/wdp # 

root@chani /home/wdp/Desktop/zfs-fuse-0.5.0 # zpool status
connect: Connection refused
Please make sure that the zfs-fuse daemon is running.
internal error: failed to initialize ZFS library
root@chani /home/wdp/Desktop/zfs-fuse-0.5.0 #

I don’t know what exactly was causing this, anyway, it seems like something with zfs-fuse as the daemon got killed by itself. i’ve seen that removing two discs from a pool is working and that the whole pool was still running. ZFS is a really really nice filesystem, if i could i would use it within my linux, but for now.. it’s probably not ready enough well. at least not zfs-fuse.

By the way, some more Information about ZFS can be obtained here:

zfs-fuse
ZFS OpenSolaris Community

And here’s a nice Video i found in Martin’s Blog:
ZFS-Video by Systemhelden

Link zum Thread Berechnung von Pi in einem Forum

Alleine die erste Seite ist schon zum weinen. Aber man soll sich über hilfesuchende nicht lustig machen. Sowas tut man nicht *kopfschyttel* gehen wir also über zu den Leuten die keine Hilfe suchen, sondern Hilfe geben.

Link zu … nunja, schaut selbst

Doof nur.. das das so gar nicht geht. Machen wir mal den Versuch: bei 1. sagt er ein rm -rf / wird rekursiv und geforced alles löschen..

wdp@chani ~ $ rm -rf /
rm: cannot remove root directory `/’
wdp@chani ~ $

Hm.. Hat nich geklappt. Und nun? Also gu

wdp@chani ~ $ mkfs.ext3 /dev/hda
mke2fs 1.41.3 (12-Oct-2008)
/dev/hda is entire device, not just one partition!
Proceed anyway? (y,n) y
mkfs.ext3: Permission denied while trying to determine filesystem size
wdp@chani ~ $

Verdammt.. Auch das klappt nicht.

wdp@chani ~ $ :(){:|:&};:
-bash: syntax error near unexpected token `{:’
wdp@chani ~ $

Ok. Dieser Trot.. Autor hat sich vertippt oder schlecht kopiert. Die Forkbomb geht nämlich wie folgt:

:(){ :|:& };:

Und ja. Der Autor hat recht, dieser Schnippsel kann den Rechner lahm legen unter gewissen Vorraussetzungen versteht sich, die meisten Distributionen haben vernünftige ulimits gesetzt (ulimit -a) mithilfe von diesen Beschränkungen macht entsprechende “forkbomb” nichts. Beispiel:

-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable

[1]+ Done : | :

Klappt also.. auch nicht. Auch die restlichen Befehle, wollen das man Root ist – Deswegen arbeitet man unter Linux niemals als Root ausser zum installieren, warten und konfigurieren des Systems als solches.

Auch nett, ist TheBonsai’s Blog dazu:

Bonsai’s Blog

http://rkhunter.sourceforge.net/

Die Ausgabe des netten Tools bei mir lokal ist übrigens:

System checks summary
=====================

File properties checks…
Required commands check failed
Files checked: 118
Suspect files: 13

Rootkit checks…
Rootkits checked : 109
Possible rootkits: 0

Applications checks…
Applications checked: 4
Suspect applications: 0

The system checks took: 2 minutes and 42 seconds