Ich habe gerade kanotix64-acritox-trialshot-121015a installiert.
Der mysql daemon mysqld läuft ständig auf ca. 100% sowie die Datei .local/share/akonadi/db_data/mysql.err wird immer voller geschrieben (wahrscheinlich bis die Platte voll ist). Nach Neustart fängt das ganze von vorne an.
Kann ich akonadi löschen, speziell akonadi-backend-mysql oder hat das Auswirkungen auf KDE? Oder wie kann ich dieses Verhalten abstellen?
Code:
du -h | grep akonadi
1,4M ./.local/share/akonadi/db_data/akonadi
212K ./.local/share/akonadi/db_data/performance_schema
4,0K ./.local/share/akonadi/db_data/test
1016K ./.local/share/akonadi/db_data/mysql
2,2G ./.local/share/akonadi/db_data
4,0K ./.local/share/akonadi/file_db_data
4,0K ./.local/share/akonadi/db_misc
2,2G ./.local/share/akona
Installiert ist:
Code:
dpkg -l | grep ii | grep akonadi
ii akonadi-backend-mysql 1.7.2-1 all MySQL storage backend for Akonadi
ii akonadi-server 1.7.2-1 amd64 Akonadi PIM storage service
ii libakonadi-contact4 4:4.8.4-1 amd64 library for using the Akonadi PIM data server
ii libakonadi-kabc4 4:4.8.4-1 amd64 library for using the Akonadi PIM data server
ii libakonadi-kcal4 4:4.8.4-1 amd64 library for using the Akonadi PIM data server
ii libakonadi-kde4 4:4.8.4-1 amd64 library for using the Akonadi PIM data server
ii libakonadi-kmime4 4:4.8.4-1 amd64 library for using the Akonadi PIM data server
ii libakonadiprotocolinternals1 1.7.2-1 amd64 libraries for the Akonadi PIM storage service
Der Inhalt der mysql.err ist ein wenig Text und überwiegend Nullen.
Code:
121018 9:01:14 [Note] Plugin 'FEDERATED' is disabled.
121018 9:01:14 InnoDB: The InnoDB memory heap is disabled
121018 9:01:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121018 9:01:14 InnoDB: Compressed tables use zlib 1.2.7
121018 9:01:14 InnoDB: Using Linux native AIO
121018 9:01:14 InnoDB: Initializing buffer pool, size = 80.0M
121018 9:01:14 InnoDB: Completed initialization of buffer pool
121018 9:01:14 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121018 9:01:14 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
121018 9:01:18 InnoDB: Waiting for the background threads to start
121018 9:01:19 InnoDB: 1.1.8 started; log sequence number 1713481
121018 9:01:20 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.24-9' socket: '/home/zerum-5/.local/share/akonadi/socket-KanotixBox/mysql.socket' port: 0 (Debian)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
121018 9:01:21 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex c30c7bd000000003ffffffffffffffff00000000001a1f6c45bf00000000000000000000000300020272800800000000020f00020005000600000
|
