View previous topic :: View next topic |
Author |
Message |
jhon987 Apprentice
Joined: 18 Nov 2013 Posts: 297
|
Posted: Sat May 24, 2014 4:07 pm Post subject: Systemd journal flush too slow |
|
|
hi,
does anyone knows why systemd journal takes so much time to flush during boot?
Code: | [ 5.588056] EXT4-fs (sda3): re-mounted. Opts: (null)
[ 5.626763] systemd-udevd[151]: starting version 208
[ 6.441114] systemd-udevd[160]: renamed network interface eth0 to enp7s0
[ 6.773814] nvidia 0000:01:00.0: irq 66 for MSI/MSI-X
[ 7.561273] Adding 1022972k swap on /dev/sda4. Priority:-1 extents:1 across:1022972k
[ 8.252175] systemd-journald[115]: Received request to flush runtime journal from PID 1
[ 26.371023] usb 2-1.6: link qh8-0e01/ffff88021507aa00 start 3 [1/2 us]
[ 31.942632] r8169 0000:07:00.0 enp7s0: link down
[ 31.942743] r8169 0000:07:00.0 enp7s0: link down
[ 33.125199] nvidia 0000:01:00.0: irq 66 for MSI/MSI-X |
as you can see it takes about 18 secs, actually I'm more interested to know how can I decrease that time?
TNX in advance |
|
Back to top |
|
|
Pearlseattle Apprentice
Joined: 04 Oct 2007 Posts: 162 Location: Switzerland
|
Posted: Thu Jun 12, 2014 7:59 pm Post subject: |
|
|
Hi
You'll probably have to post detailed informations about the device on which systemd writes (e.g. HDD, SSD, Flash, ...tape?), its connection (e.g. local sata, usb, etc..) its filesytem and its mount options (e.g. output of "mount").
Additionally, as I have absolutely no clue about systemd, I want to challenge your statement :
how did you come to the conclusion that "[ 26.371023] usb 2-1.6: link qh8-0e01/ffff88021507aa00 start 3 [1/2 us] " happens only then because it waits for the journal flush and not for other dependencies (e.g. network availability)?
Thx |
|
Back to top |
|
|
jhon987 Apprentice
Joined: 18 Nov 2013 Posts: 297
|
Posted: Fri Jun 13, 2014 6:46 am Post subject: |
|
|
Pearlseattle wrote: | Hi
You'll probably have to post detailed informations about the device on which systemd writes (e.g. HDD, SSD, Flash, ...tape?), its connection (e.g. local sata, usb, etc..) its filesytem and its mount options (e.g. output of "mount").
Additionally, as I have absolutely no clue about systemd, I want to challenge your statement :
how did you come to the conclusion that "[ 26.371023] usb 2-1.6: link qh8-0e01/ffff88021507aa00 start 3 [1/2 us] " happens only then because it waits for the journal flush and not for other dependencies (e.g. network availability)?
Thx |
Hi,
thanks for replying (even if a bit late then I expected) I actually already solved this one on my own. it was the journal fault I can tell you that, once I changed the name of the journal folder - making it non-writable, the delay was gone.
However, since then I come up with a more elegant solution which might be of service to others who reads this: there's a file in /etc/systemd/ called journald.conf, inside there should be already commented out - a line which sets the maximum size of the journal log file (if it's not there, create it) just enter: SystemMaxUse=<VALUE YOU CHOOSE>. i set it to 50M. I'm afraid that when the journal log gets to big its flushing start to really slow the system....
Edit: actually it's probably not flushing the journal but going over it or doing some other thing with it (because afterwards the journal information is still there i.e. it's not flushed). I came up with the flushing thing after I read some other thread in another forum which mentioned it... |
|
Back to top |
|
|
Pearlseattle Apprentice
Joined: 04 Oct 2007 Posts: 162 Location: Switzerland
|
Posted: Fri Jun 13, 2014 8:09 pm Post subject: |
|
|
Quote: | thanks for replying (even if a bit late then I expected) |
Uh, you're right, hehe... - didn't check the date of the post
Cheers |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|