Comment # 8 on bug 915575 from Tom���� Chv��tal

Yeah seems my first assessment that journald is to be blamed was wrong...
But still some blk problem stands as it fails to boot with systemd-210 as per
the logs. Updated the bug summary accordingly, not sure wether we should let
the kernel guys look or if it is soely systemd bug.

FWIW the journald status:

dreamcrawler:~ # LC_ALL=C systemctl status systemd-journald
systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
   Active: active (running) since Mon 2015-02-02 16:51:08 CET; 2min 17s ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 408 (systemd-journal)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-journald.service                               
           `-408 /usr/lib/systemd/systemd-journald                              

Feb 02 16:51:08 dreamcrawler systemd-journal[408]: Runtime journal is using
8.0M (max allowed 390.8M, trying to leave 586.3M free of 3.8G available ���
current limit 390.8M).                  
Feb 02 16:51:08 dreamcrawler systemd-journal[408]: Runtime journal is using
8.0M (max allowed 390.8M, trying to leave 586.3M free of 3.8G available ���
current limit 390.8M).                  
Feb 02 16:51:08 dreamcrawler systemd-journal[408]: Journal started              
Feb 02 16:51:16 dreamcrawler systemd-journal[408]: Permanent journal is using
1.1G (max allowed 3.9G, trying to leave 4.0G free of 31.7G available ��� current
limit 3.9G).                     
Feb 02 16:51:16 dreamcrawler systemd-journal[408]: Time spent on flushing to
/var is 164.148ms for 981 entries.