Re: Why do we have a default activated man-db.timer?

2019-02-17 Thread Tom Bachreier
Hi Étienne! Thanks for your comprehensive explanation. I appreciate it very much. Feb 12, 2019, 1:38 AM by etienne.moll...@mailoo.org: > Tom Bachreier, on 2019-02-11: > >> BUT wait... >> >> I was wondering why do we have man-db.timer in the first place? >> >

Re: Bug with soft raid?

2019-02-12 Thread Tom Bachreier
Feb 12, 2019, 12:08 PM by dl...@bluewin.ch: > Hi There, > > Here is what I get on my up to date stretch box: > > Feb 10 12:19:12 box kernel: [ 7734.562060] INFO: task md0_raid1:461 blocked > for more than 120 seconds. > [...] > Feb 10 12:19:12 box kernel: [ 7734.562192] INFO: task md1_raid1:4

Why do we have a default activated man-db.timer?

2019-02-10 Thread Tom Bachreier
System: Testing Hi! With the migration of man-db 2.8.5-1 into testing about a month ago I get bothered once a day with a lot of useless lines in syslog: > Feb 10 00:00:51 osprey mandb[3543]: Purging old database entries in > /usr/share/man... > Feb 10 00:00:51 osprey mandb[3543]: Processing manu

Re: E: Unable to locate package zimlib . . .

2019-01-15 Thread Tom Bachreier
Hi! Jan 16, 2019, 8:00 AM by lbrt...@gmail.com: > Why is it I can't install zimlib? > I don't know what zimlib is but you mean maybe libzim? In stretch is libzim0v5: Tom

Re: Software RAID blocks

2019-01-13 Thread Tom Bachreier
Hi Reco! Jan 13, 2019, 1:47 PM by recovery...@enotuniq.net: > On Sun, Jan 13, 2019 at 01:20:50PM +0100, Tom Bachreier wrote: > >> Jan 13, 2019, 12:46 PM by >> recovery...@enotuniq.net >> <mailto:recovery...@enotuniq.net>>> : >> >> > On S

Re: Software RAID blocks

2019-01-13 Thread Tom Bachreier
Hi Reco! Jan 13, 2019, 12:46 PM by recovery...@enotuniq.net: > On Sun, Jan 13, 2019 at 12:27:19PM +0100, Tom Bachreier wrote: > >> TLDR; >> My /home on dmcrypt -> software Raid5 blocks irregular usually without >> any error messages. >> >> I can get

Software RAID blocks

2019-01-13 Thread Tom Bachreier
Hi! TLDR; My /home on dmcrypt -> software Raid5 blocks irregular usually without any error messages. I can get it going again with "fdisk -l /dev/sdx". Do you have an ideas how I can debug this issue further? Is it a dmcrypt, a dm-softraid or a hardware issue? --