dynaDAT | UNIXoni | REDATEK | ITVeteran - wiki

adaptec_logicaldrive

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:47:11+00:00

Austausch von Festplatten und Erstellen eines neuen Logical Drives mit arcconf

Dieser Beitrag beschreibt, wie man ein defektes Logical Drive ersetzt, indem alle vier Festplatten (HDDs) ausgetauscht werden. Achte darauf, dass alle Festplatten vom gleichen Typ sind, da unterschiedliche Laufwerksgeometrien zu Ausfällen führen können.

Das Tool „arcconf“ kann von der offiziellen Seite von ADAPTEC heruntergeladen werden: ADAPTEC RAID 6805E Downloadseite

Schritt-für-Schritt-Anleitung

1. Logical Drive löschen Um das bestehende Logical Drive zu löschen, nutze den folgenden Befehl:

  
  linux_x64/arcconf delete 1 logicaldrive 2

2. Überprüfen des HDD-Status Prüfe nach dem Löschen des Logical Drives, ob alle Festplatten im Status „Ready“ zur Verfügung stehen:

 
  linux_x64/arcconf getconfig 1

3. Neues Logical Drive erstellen Erstelle ein neues Logical Drive mit den folgenden Parametern:

  
  linux_x64/arcconf create 1 logicaldrive max 10 0 4 0 5 0 6 0 7

4. Status des neuen Drives überprüfen Stelle sicher, dass das neu erstellte Logical Drive den Status „optimal“ hat:

  
  linux_x64/arcconf getconfig 1 ld

Wichtige Hinweise

Achte darauf, dass alle Festplatten vom gleichen Typ sind.
Unterschiedliche Laufwerksgeometrien können zu Ausfällen führen.
Verwende immer die aktuellste Version von arcconf.

Durch diese Schritte wird ein neues Logical Drive mit den ausgetauschten Festplatten erstellt und korrekt konfiguriert.

Stichworte

Adaptec, arcconf, RAID, Logical Drive, HDD, 6805E

ausfall_raid_hdd

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:47:02+00:00

arcconf – Arbeiten mit RAID-Volumes unter Linux

Ein Logical Drive (LD) meldet eine ausgefallene Festplatte (HDD). Die folgenden Schritte helfen bei der Diagnose und Reparatur mittels `arcconf`.

1. Rescan aller Devices

Führt eine erneute Erkennung aller Geräte durch.

linux_x64/arcconf rescan 1

2. Rebuild anstoßen (wenn automatisch möglich)

Ein funktionierender Versuch:

linux_x64/arcconf task start 1 device 0 initialize
linux_x64/arcconf rescan 1

→ Danach begann automatisch ein Rebuild.

3. Device feststellen

Listet physikalische und logische Geräte auf.

linux_x64/arcconf getconfig 1 pd

Hinweis: * PD = Physical Device * LD = Logical Device

4. Device löschen (clear)

Setzt ein Device zurück (z. B. nach Austausch oder Fehlerstatus). Achtung: Vorher Device-Nummer herausfinden über `getconfig`.

linux_x64/arcconf task start 1 device 0 1 clear

→ Syntax: `device <Channel> <Device>`

5. Device prüfen oder reparieren

linux_x64/arcconf task start 1 device 0 0 verify
linux_x64/arcconf task start 1 device 0 0 verify_fix

6. Danach: Devices erneut scannen

linux_x64/arcconf rescan 1

7. Logical Drive prüfen

linux_x64/arcconf task start 1 logicaldrive 0 verify_fix

8. HDD austauschen und identifizieren

Lässt die LED des betreffenden Geräts blinken, zur physischen Identifikation.

linux_x64/arcconf identify 1 device 0 0

Hinweise

Immer vorher aktuelle Konfiguration sichern.
Im Zweifel zuerst `getconfig` nutzen.
Prüfen, ob „hot spare“ eingerichtet ist.
Rebuild-Status regelmäßig beobachten mit:

  linux_x64/arcconf getstatus 1

Stichworte

RAID, arcconf, Adaptec, Logical Drive, HDD, Rebuild, Linux

dokuwiki

Anonymous (anonymous@undisclosed.example.com) — 2026-06-20T03:58:46+00:00

DokuWiki

DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki.

Read the DokuWiki Manual to unleash the full power of DokuWiki.

Download

DokuWiki is available at https://download.dokuwiki.org/

All documentation and additional information besides the syntax description is maintained in the DokuWiki at www.dokuwiki.org.

About DokuWiki

Installing DokuWiki

Using DokuWiki

Customizing DokuWiki

DokuWiki Feedback and Community

Copyright

2004-2020 © Andreas Gohr andi@splitbrain.org¹⁾ and the DokuWiki Community

The DokuWiki engine is licensed under GNU General Public License Version 2. If you use DokuWiki in your company, consider donating a few bucks .

Not sure what this means? See the FAQ on the Licenses.

¹⁾

Please do not contact me for help and support – use the mailinglist or forum instead

informix_rowid

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:46:59+00:00

Nutzung der rowid in SQL Statements

Die Verwendung der `rowid` in SQL-Statements sollte mit Vorsicht erfolgen und nach Möglichkeit vermieden werden. Dies gilt insbesondere im Kontext von Datenbankmigrationen oder bei der Verwendung von Datenbank-Wrapping-Technologien wie z.B. dem Informix-Wrapper für PostgreSQL.

Laut IBM-Dokumentation wird empfohlen, sich nicht auf `rowid` zu verlassen, da sie systemabhängig ist und sich unter bestimmten Umständen ändern kann. (vgl. https://www.ibm.com/docs/de/informix-servers/12.10.0?topic=statements-rowid-values-in-select)

In Informix ist `rowid` ein Integer-Wert. In PostgreSQL gibt es kein direktes Äquivalent, aber es existiert die systeminterne Spalte `ctid`, die eine ähnliche Funktion übernimmt. (vgl. https://www.enterprisedb.com/postgres-tutorials/what-equivalent-rowid-postgresql?lang=en und https://www.postgresql.org/docs/current/ddl-system-columns.html)

Unterschiede zwischen Informix rowid und PostgreSQL ctid

Der Informix-Wrapper leitet die `rowid` grundsätzlich an die PostgreSQL-`ctid` weiter. Dabei gibt es jedoch wichtige technische Unterschiede:

`rowid` in Informix ist ein einfacher Integer.
`ctid` in PostgreSQL ist ein Tupel bestehend aus (page_number, tuple_index).
Der Informix-Wrapper setzt `rowid` auf den ersten Wert von `ctid`, also ergibt sich die übergebene Form: `ctid = (rowid, 0)`.

Technische Eigenschaften der ctid in PostgreSQL

`ctid` ändert sich bei jeder UPDATE-Operation.
Wird durch VACUUM FULL neu zugewiesen.
Kann nach VACUUM ANALYZE wiederverwendet werden.
Ist systemintern und nicht als dauerhaft eindeutiger Schlüssel geeignet.

Beste Praktiken

Statt `rowid` oder `ctid` zu verwenden, sollten möglichst logische Identifikatoren eingesetzt werden. Empfohlene Alternativen:

Primärschlüssel nutzen (z.B. durch `SERIAL` oder `BIGSERIAL` erzeugt).
Aufbau geeigneter Indexstrukturen zur Performanceoptimierung.
Logische Referenzen statt physischer Adressen (z.B. Foreign Keys auf Primärschlüssel).
Anpassung der Anwendung, um auf `rowid`/`ctid` zu verzichten.

Mögliche Lösungen bei Migration oder Wrapper-Nutzung

Wenn eine bestehende Anwendung auf `rowid` angewiesen ist, gibt es folgende Workarounds:

Anlage einer eigenen physischen Spalte `rowid` vom Typ `BIGSERIAL` in der PostgreSQL-Zielstruktur.
Aufbau eines dedizierten Index zur effizienten Suche.
Anpassung der SQL-Statements in der Anwendung, um die neue Struktur zu unterstützen.

Hinweis: Die Verwendung von `ctid` als langfristiger Zeilenidentifikator sollte vermieden werden, da er sich durch normale Datenbankoperationen wie `UPDATE`, `VACUUM`, etc. verändern kann und somit nicht stabil ist.

Fazit

Die `rowid` bzw. `ctid` sind für temporäre oder systeminterne Zwecke nützlich, sollten jedoch nicht als zuverlässige Referenz in langlebigen Anwendungen oder Datenmodellen verwendet werden. Stattdessen ist auf Primärschlüssel-basierte Logik umzusteigen.

Stichworte

Informix, PostgreSQL, rowid, ctid, FDW, Migration, Primärschlüssel

iphone_video

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:47:12+00:00

iPhone Video (.mov) in MP4 umwandeln

Der, für mich, einfachste Weg:

  ffmpeg -i 'iPhone.mov' -vcodec h264 -acodec mp2 video.mp4

Stichworte

ffmpeg, iPhone, MOV, MP4, Video, Konvertierung

letsencrypt_webpath_docker_renew

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:46:47+00:00

Apache Konfiguration für Let's Encrypt Zertifikats-Erneuerung mit Podman

Um Let's Encrypt Zertifikate in einem Container zu erneuern, ist eine spezifische Konfiguration des Apache Virtual Hosts erforderlich, da die Zertifikatserneuerung über einen Container erfolgt. Die folgende Konfiguration stellt sicher, dass Anfragen an die /.well-known/acme-challenge-Ressourcen erfolgreich verarbeitet werden, selbst wenn der eigentliche DocumentRoot für die Webseite anders gesetzt ist.

Apache VHost Konfiguration

In der Apache-Konfigurationsdatei des Virtual Hosts wird der DocumentRoot auf das Verzeichnis der Webseite gesetzt. Da Let's Encrypt jedoch auf /.well-known/acme-challenge zugreift, um die Zertifikate zu validieren, ist eine Alias-Direktive erforderlich, um Anfragen korrekt umzuleiten. Der relevante Ausschnitt der Konfiguration:

.... <VirtualHost *:80> 
DocumentRoot /var/www/html/redatek 
Alias /.well-known/acme-challenge/ /var/www/html/.well-known/acme-challenge/ 
... </VirtualHost>

Erklärung:

DocumentRoot legt das Verzeichnis fest, das die Hauptinhalte der Webseite enthält. In diesem Beispiel: `/var/www/html/redatek`.
Alias definiert eine Umleitung für das Verzeichnis /.well-known/acme-challenge/ auf `/var/www/html/.well-known/acme-challenge/`. Dadurch können Let's Encrypt Validierungsanfragen unabhängig vom DocumentRoot beantwortet werden.

Beachten im Containerbetrieb

Apache Config für http (80) anpassen:

<If "%{THE_REQUEST} !~ m# /.well-known/?#i">
       RedirectPermanent / https://url.tld/
</If>

Zumindest Apache > 2.4

Zertifikat generieren

den Webroot Ordner angeben –> certbot certonly –webroot /var/www/ -d domain.tld

Let's Encrypt Zertifikats-Erneuerung im Container

Da die Zertifikatserneuerung über Podman in einem Container stattfindet, wird das Verzeichnis für die Webseiten-Validierung gemountet. Dies erfolgt mittels Volumemapping, um sicherzustellen, dass Let's Encrypt auf die notwendigen Verzeichnisse zugreifen kann.

Der Befehl für die Zertifikats-Erneuerung im Container sieht wie folgt aus:

podman run --rm -it
-v "/container/letsencrypt/log:/var/log/letsencrypt"
-v "/var/www/html:/var/www/"
-v "/container/letsencrypt/cert:/etc/letsencrypt"
docker.io/certbot/certbot renew

Erklärung:

–rm löscht den Container nach der Ausführung, um Speicherplatz freizugeben.
-it ermöglicht eine interaktive Ausführung im Terminal.
-v „/container/letsencrypt/log:/var/log/letsencrypt“ legt das Log-Verzeichnis fest, um Protokolle der Zertifikats-Erneuerung zu speichern.
-v „/var/www/html:/var/www/„ mappt das lokale Webverzeichnis `/var/www/html` in das Verzeichnis `/var/www/` innerhalb des Containers.
-v “/container/letsencrypt/cert:/etc/letsencrypt“ weist das Verzeichnis für die Zertifikate zu.

Neustart nicht vergessen

nach dem

podman run --rm -it -v "/container/letsencrypt/log:/var/log/letsencrypt" -v "/var/www/html:/var/www/" -v "/container/letsencrypt/cert:/etc/letsencrypt" docker.io/certbot/certbot renew -v

unbedingt die betreffenden Dienste neu starten damit der neue Key aktiv geladen wird.

systemctl restart httpd
podman container restart mailserver

Problematik ohne Alias-Direktive

Ohne das Alias-Mapping schlägt der Erneuerungsprozess fehl, da Let's Encrypt auf /.well-known/acme-challenge zugreifen muss. Der angegebene DocumentRoot für die Webseite (/var/www/html/redatek) enthält jedoch dieses Verzeichnis nicht direkt. Daher ist das Alias in der Apache-Konfiguration notwendig, um die Validierung erfolgreich abzuschließen.

Zusammenfassung

Diese Konfiguration ermöglicht es, Let's Encrypt Zertifikate über einen Podman-Container zu erneuern, indem die Apache-Konfiguration angepasst wird, um die notwendigen Ressourcen bereitzustellen.

DocumentRoot verweist auf den Hauptinhalt der Webseite.
Alias stellt sicher, dass die Zertifikatsanfragen von Let's Encrypt korrekt beantwortet werden.
Podman Container-Setup mit Volumemapping ermöglicht den Zugriff auf die Verzeichnisse für Logs und Zertifikate sowie auf das Webverzeichnis für die Validierung.

Stichworte

Let's Encrypt, ACME, Apache, Alias, VirtualHost, certbot, Podman, Docker, Zertifikat, /.well-known

syntax

Anonymous (anonymous@undisclosed.example.com) — 2026-06-20T03:58:46+00:00

Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing „Edit this page“. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

Basic Text Formatting

DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these.

DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
Of course you can **__//''combine''//__** all these.

You can use _subscript and ^superscript, too.

You can use <sub>subscript</sub> and <sup>superscript</sup>, too.

You can mark something as ~~deleted~~ as well.

You can mark something as <del>deleted</del> as well.

Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.

This is some text with some linebreaks
Note that the two backslashes are only recognized at the end of a line
or followed by
a whitespace \\this happens without it.

This is some text with some linebreaks\\ Note that the
two backslashes are only recognized at the end of a line\\
or followed by\\ a whitespace \\this happens without it.

You should use forced newlines only if really needed.

Links

DokuWiki supports multiple ways of creating links.

External

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too.

DokuWiki supports multiple ways of creating links. External links are recognized
automagically: http://www.google.com or simply www.google.com - You can set
link text as well: [[http://www.google.com|This Link points to google]]. Email
addresses like this one: <andi@splitbrain.org> are recognized, too.

Internal

Internal links are created by using square brackets. You can either just give a pagename or use an additional link text.

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|link text]].

Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

You can use namespaces by using a colon in the pagename.

You can use [[some:namespaces]] by using a colon in the pagename.

For details about namespaces see namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section.

This links to [[syntax#internal|this Section]].

Notes:

Links to existing pages are shown in a different style from nonexisting ones.
DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled.
When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.

Interwiki

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki.

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

Windows Shares

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet.

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the „local zone“).
For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):
conf/lang/en/lang.php
```
<?php
/**
 * Customization of the english language file
 * Copy only the strings that needs to be modified
 */
$lang['js']['nosmblinks'] = '';
```

Image Links

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this:

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

Footnotes

You can add footnotes ¹⁾ by using double parentheses.

You can add footnotes ((This is a footnote)) by using double parentheses.

Sectioning

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

Headline Level 3

Headline Level 4

Headline Level 5

==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

Media Files

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height²⁾:

Resized external image:

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{https://www.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment.

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

Supported Media Formats

DokuWiki can embed the following media formats directly.

Image	`gif`, `jpg`, `png`
Video	`webm`, `ogv`, `mp4`
Audio	`ogg`, `mp3`, `wav`
Flash	`swf`

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Fallback Formats

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video:

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a „poster“ image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Lists

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

This is a list
The second item
- You may have different levels
Another item

The same list but ordered
Another item
1. Just use indention for deeper levels
That's it

  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

Text Conversions

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

Text to Image Conversions

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

8-)
8-O
:-(
:-)
=)
:-/
:-\
:-?
:-D
:-P
:-O
:-X
:-|
;-)
^_^
m(
:?:
:!:
LOL
FIXME
DELETEME

Text to HTML Conversions

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® „He thought 'It's a man's world'…“

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and „double quotes“. They can be turned off through a config option.

Quoting

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't

Well, I say we should

Really?

Yes!

Then lets do it!

Tables

DokuWiki supports a simple syntax to create tables.

Heading 1	Heading 2	Heading 3
Row 1 Col 1	Row 1 Col 2	Row 1 Col 3
Row 2 Col 1	some colspan (note the double pipe)
Row 3 Col 1	Row 3 Col 2	Row 3 Col 3

Table rows have to start and end with a | for normal rows or a ^ for headers.

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

	Heading 1	Heading 2
Heading 3	Row 1 Col 2	Row 1 Col 3
Heading 4	no colspan this time
Heading 5	Row 2 Col 2	Row 2 Col 3

As you can see, it's the cell separator before a cell which decides about the formatting:

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Heading 1	Heading 2	Heading 3
Row 1 Col 1	this cell spans vertically	Row 1 Col 3
Row 2 Col 1		Row 2 Col 3
Row 3 Col 1		Row 2 Col 3

Apart from the rowspan syntax those cells should not contain anything else.

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

Table with alignment
right	center	left
left	right	center
xxxxxxxxxxxx	xxxxxxxxxxxx	xxxxxxxxxxxx

This is how it looks in the source:

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

No Formatting

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. The same is true for //__this__ text// with a smiley ;-).

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

Code Blocks

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>.

This is text is indented by two spaces.

This is preformatted code all spaces are preserved: like              <-this

This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source:

  This is text is indented by two spaces.

<code>
This is preformatted code all spaces are preserved: like              <-this
</code>

<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>

Syntax Highlighting

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>.

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic

There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers.

Downloadable Code Blocks

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this:

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>

myexample.php

<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

RSS/ATOM Feed Aggregation

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

Parameter	Description
any number	will be used as maximum number items to show, defaults to 8
reverse	display the last items in the feed first
author	show item authors names
date	show item dates
description	show the item description. All HTML tags will be stripped
nosort	do not sort the items in the feed
n[dhm]	refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours).

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example:

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

Your Brain Can Rewire Itself To Allow True Multitasking von BeauHD (2026/07/29 09:00)
Trump Administration Bans New Chinese Humanoid Robots von BeauHD (2026/07/29 05:30)
Workplaces Look For Cheaper AI As 'Tokenmaxxing' Fades As a Corporate Fad von BeauHD (2026/07/29 03:30)
Apple Retires iPhone Upgrade Program For Klarna-Backed Leases von BeauHD (2026/07/28 23:00)
AI-Found Bugs Aren't Proving Any Easier to Exploit Despite the Hype von BeauHD (2026/07/28 22:00)

Control Macros

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

Macro	Description
~~NOTOC~~	If this macro is found on the page, no table of contents will be created
~~NOCACHE~~	DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call

Syntax Plugins

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

Info Plugin 2020-06-04 von Andreas Gohr
Displays information about various DokuWiki internals

¹⁾

This is a footnote

²⁾

when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing

welcome

Anonymous (anonymous@undisclosed.example.com) — 2026-06-20T03:58:46+00:00

Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,
– the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: start.

Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the syntax page.

You might also want to use a sidebar. To create it, just edit the sidebar page. Everything in that page will be shown in a margin column on the side. Read our FAQ on sidebars to learn more.

Please be aware that not all templates support sidebars.

Customize your Wiki

Once you're comfortable with creating and editing pages you might want to have a look at the configuration settings (be sure to login as superuser first).

You may also want to see what plugins and templates are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.

Join the Community

DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the newsletter.

The DokuWiki User Forum is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get support.

Of course we'd be more than happy to have you getting involved with DokuWiki.

xfs_error_kernel

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T06:46:56+00:00

XFS Fehler nach Kernel-Update

Fehlerbeschreibung

Nach einem Update auf folgenden Kernel:

Linux 4.18.0-553.58.1.el8_10.x86_64

trat beim Booten bzw. Mounten des XFS-Dateisystems folgender Fehler auf:

`kernel: XFS (dm-0): Corruption detected. Unmount and run xfs_repair`
`kernel: XFS (dm-0): Internal error i != 1 at line 481 of file fs/xfs/libxfs/xfs_alloc.c. Caller xfs_alloc_fixup_trees+0x198/0x3b0 [xfs]`

Änderungen an Kernel-Konfiguration

In der Datei `config-4.18.0-553.58.1.el8_10.x86_64` wurden folgende Optionen aktiviert:

CONFIG_XFS_FS=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_XFS_ONLINE_SCRUB=y

Analyse & Hintergrundwissen

Fehlerursache: Der Fehler `i != 1` in `xfs_alloc.c` deutet auf eine Inkonsistenz in den freien Speicherbaumstrukturen des Dateisystems hin. Dies kann durch eine beschädigte Metastruktur oder durch eine fehlerhafte Kernel-Implementierung ausgelöst werden.
xfs_repair: Das Tool `xfs_repair` sollte verwendet werden, um die Dateisystemstruktur zu prüfen und zu reparieren. Wichtig: Das Dateisystem muss vorher ausgehängt werden.
CONFIG_XFS_RT: Aktiviert Unterstützung für „Real-Time Subvolumes“, eine selten genutzte Funktion. Falls nicht benötigt, kann sie deaktiviert werden, um Komplexität zu reduzieren.
CONFIG_XFS_ONLINE_SCRUB: Ermöglicht die Online-Prüfung von Dateisystemstrukturen. Diese Funktion ist experimentell und kann bei bestimmten Kernel-Versionen instabil sein.
Kernel-Kompatibilität: Änderungen an XFS-bezogenen Optionen können zu Inkompatibilitäten mit bestehenden Dateisystemen führen, insbesondere wenn das Dateisystem mit einem älteren Kernel erstellt wurde.

Empfehlung

System im Rescue-Modus starten.
betroffene Partition aushängen (`umount /dev/dm-0`)
`xfs_repair /dev/dm-0` ausführen.
Bei wiederholtem Auftreten: Kernel-Konfiguration prüfen, insbesondere experimentelle Optionen wie `CONFIG_XFS_RT` und `CONFIG_XFS_ONLINE_SCRUB`.
Backup wichtiger Daten vor weiteren Tests!

In meinem konkreten Fall war das root Filesystem betroffen und ich bin das Risiko, ohne xfs_repair auf ausgegangenem Device, mit geänderter Konfiguration neu zu starten, eingegangen.

Quellen & Tools

`man xfs_repair`
https://xfs.org
Kernel-Quellcode: `fs/xfs/libxfs/xfs_alloc.c`

Stichworte

XFS, Kernel, RHEL, EL8, xfs_repair, Filesystem, Korruption, CONFIG_XFS_RT, Rescue

dynaDAT | UNIXoni | REDATEK | ITVeteran - wiki

adaptec_logicaldrive

Austausch von Festplatten und Erstellen eines neuen Logical Drives mit arcconf

Schritt-für-Schritt-Anleitung

Wichtige Hinweise

Stichworte

ausfall_raid_hdd

arcconf – Arbeiten mit RAID-Volumes unter Linux

1. Rescan aller Devices

2. Rebuild anstoßen (wenn automatisch möglich)

3. Device feststellen

4. Device löschen (clear)

5. Device prüfen oder reparieren

6. Danach: Devices erneut scannen

7. Logical Drive prüfen

8. HDD austauschen und identifizieren

Hinweise

Stichworte

dokuwiki

DokuWiki

Download

Read More

Copyright

informix_rowid

Nutzung der rowid in SQL Statements

Unterschiede zwischen Informix rowid und PostgreSQL ctid

Technische Eigenschaften der ctid in PostgreSQL

Beste Praktiken

Mögliche Lösungen bei Migration oder Wrapper-Nutzung

Fazit

Stichworte

iphone_video

iPhone Video (.mov) in MP4 umwandeln

Stichworte

letsencrypt_webpath_docker_renew

Apache Konfiguration für Let's Encrypt Zertifikats-Erneuerung mit Podman

Apache VHost Konfiguration

Beachten im Containerbetrieb

Zertifikat generieren

Let's Encrypt Zertifikats-Erneuerung im Container

Neustart nicht vergessen

Problematik ohne Alias-Direktive

Zusammenfassung

Stichworte

syntax

Formatting Syntax

Basic Text Formatting

Links

External

Internal

Interwiki

Windows Shares

Image Links

Footnotes

Sectioning

Headline Level 3

Headline Level 4

Headline Level 5

Media Files

Supported Media Formats

Fallback Formats

Lists

Text Conversions

Text to Image Conversions

Text to HTML Conversions

Quoting

Tables

No Formatting

Code Blocks

Syntax Highlighting

Downloadable Code Blocks

RSS/ATOM Feed Aggregation

Control Macros

Syntax Plugins

welcome

Welcome to your new DokuWiki

Create your first pages

Customize your Wiki

Join the Community

xfs_error_kernel