Every now and then I’m visting my best friend’s mom (generation > 50a) to update
her old Pentium 4 system with the last opensuse software. Each time,
I have to restore her Desktop to provide the basic features like managing opened
windows, add the clock again, etc. Each time, I pay carefully attention to lock
the screen afterwards. Sometimes I get doubts, that they are just fooling me, but my
friend declined this, of course.
This time they disarranged the screen in a very extreme way1. Take it for amusement
or for considering a clearer warning of unlocking the screen. I vote for:
You might end with a coruppted system!
Please copy this into the form field below:
I asked my son’s friend and got his permission.
Did you recognize these empty plasma panels on each edge of the screen
which prevents all application to get maximized properly? ↩︎
Are you also sometimes annoyed by only finding documents on http://scribd.com and
nowhere else? Furthermore this site is missing of a download or printing
opportunity – at least there is no one for ordinary vitors.
Fortunately there is a little trick which might help you to still download a
pdf:
For mobile visitors using a mobile browser (tested with Opera Mini), there is a
download button. You just have to:
use Firefox
Tell scribd untruly, that you are using Opera Mini
open a new tab, enter about:config in the address bar and go for it
accept the security hint
use the context menu to create a new string named general.useragent.override
set the value of this string to Opera/9.80 (J2ME/MIDP; Opera Mini/6.24288/25.729; U; en) Presto/2.5.25 Version/10.54
visit the scribd page again and use the now appearing download button to reveive your pdf.
you should reset this string afterwards again to an empty value
When updating my only productive computer system to the latest opensuse
version 12.1, I decided to give the feature rich, shiny new filesystem
btrfs a try. It’s not yet so stable, but it is already delivered by
all main distribution. Fedora actually wants to use it as default.
Up to now I have to evaluate this disission to be more risky than lucky. After
something like two month, I experienced two filesystem corruptions. The first
one hit my root-filesystem. I had to setup my system from scratch, because every
write attempt on the partition ended with a kernel failure, most probably caused
by the btrfs driver. Mounting the partition in read-only mode while using a
Live-CD was the only way to do a late backup.
Yesterday I ran into btrfs problems again. I copied some photos to my hard disk.
In the next moment, I got some weird kernel sys messages, that didn’t help me at
all.
Message from syslogd@theta at Dec 9 17:45:00 ...
[Freitag, 9. Dezember 2011] [17:45:10] <saLOUt> kernel:[ 454.807770] Code: e9 8c fe ff ff 66 0f 1f 44 00 00 b8 ea ff ff ff e9 cf fe ff ff 48 89 de 4c 89 f7 89 04 24 e8 80 ec ff ff 8b 04 24 e9 b9 fe ff ff <0f> 0b 0f 0b 0f 1f 40 00 41 57 49 89 f7 41 56 41 55 41 54 55 53
All apps accessing my picture btrfs subvolume were crashing.
After disabling the whole btrfs system by commenting the appropriate lines in my
/etc/fstab file, I had a stable system again – just without any pictures.
Data Rescue
Luckily Chris Mason (#cmason) from #btrfs could help me to fix these
problems without any loss of data!
A# simple btrfsck didn’t help me, because of a crash of the repair tool itself:
which went without any errors. After that I used the custom build btrfs-zero-log
tool to do some btrfs magic, that I don’t understand.
./btrfs-zero-log [device]
After another reboot, I was able to mount my picture partition in read-only mode.
I did a late backup again. When reading these files, one gets usually a lot of
errors in /var/log/messages like this:
csum is the abbreviation for checksum. ino means inode, which is a kind of
identifier for every file. To fix these errors, you have to find these files
belonging to these inodes, deleting them and copy them back from your backup.
I wrote a small ruby script, which helps you finding the affected files
#!/usr/bin/ruby# string with error messageserror_messages=`dmesg | grep "found for inode"`# list of integersinode_list=error_messages.split("\n").map{|i|i.match(/inode (\d+).*/)[1].to_i}# list of arrays of filenamesfile_list=inode_list.map{|i|`find /mnt/test -inum #{i}`.split("\n")}# require 'json'# File.open("/tmp/inode-files.json", "w") {|f| f << JSON.pretty_generate(file_list)}putsfile_list.flatten.uniq.sort.join("\n")
If you finally want to delete these files, you have to remount your partition in
read-write mode.
At least for me, this walkthrough suggested by Chris resolved my problems.
Als ich gefragt wurde, ob ich am Heiligen1 Abend 2010 den
Weihnachtsmann vertreten würde, habe ich mir gleich überlegt,
auch ein Gedicht vortragen zu wollen, um die kleinen Kinder
ein wenig anzuspornen.
Nachdem der Vorsatz rechtzeitig gefasst war, hat mir jedoch etwas
Zeit zur Realisierung gefehlt. Ja, der Reim ist nicht perfekt, aber
hey: Die Kinder haben ja auch keine Ahnung.
Problematischer war dann noch die Präsentation. Die Vertretung des
Weihnachtsmanns war viel zu aufgeregt – war die Rolle doch vollkommen
neu. So ein Mist: Ich hatte damals ein Blackout. :(
Ich bin jetzt beim Sortieren wieder auf den Text gestoßen und veröffentliche
ihn hier unter der CC BY-NC-SA-Lizenz, damit es nicht ganz umsonst war. Auf
Namensnennung (BY) mag bei eurem Auftritt verzichtet werden. Sonst würde
schließlich eure Tarnung als Weihnachtsmann auffliegen. Toll nicht? Ich habe
echt an alles gedacht!
Weihnachtsmann-Gedicht
Von Himmelspforte froh und munter,
fahr’ ich mit dem Schlitten runter.
Doch meine Rentiere 12 Stück,
die lass ich im Wald zurück.
Aber mein Sack, der ist so schwer,
ganz allein’ trag’ ich ihn her.
Ich bin schon alt, mich schmerzt der Rücken,
möcht’ ich euch mit Gaben nun entzücken.
Erlaubet mir zuvor zu fragen,
kann ich was zum sitzen haben.
Die Kinder beschenke ich besonders gerne,
seh’ ich sie doch immer aus der Ferne.
Glaubt mir ja nicht, ich wüsste nicht Bescheid,
ob ihr auch immer lieb und artig seid.
Für mich ist dieser Abend natürlich nicht heilig! ↩︎
