You are not logged in.

#1 2013-03-20 10:00:05

bergqvistjl
Member
Registered: 2011-01-05
Posts: 59

systemd error "File passed too large. Ignoring." How do I fix this?

Hi, i've noticed that my dmesg is cluttured up with many instances of this: "systemd-journald[132]: File passed too large. Ignoring." usually every few minutes, which also appears on the console and disrupts what i'm working on. Is there anyway to get rid of this, and/or find the offending process that's causing it? It doesn't appear in the journalctl logs, only in dmesg, and on the console.

Offline

#2 2013-03-20 10:33:06

cle1109
Member
Registered: 2012-10-15
Posts: 7

Re: systemd error "File passed too large. Ignoring." How do I fix this?

Same thing here. I usually see it when logging out and back in, right before KDM starts up.

Offline

#3 2013-03-30 11:14:46

xdeusx
Member
Registered: 2007-10-15
Posts: 168

Re: systemd error "File passed too large. Ignoring." How do I fix this?

Happens to me too sometimes...
[ 3022.061737] systemd-journald[124]: File passed too large. Ignoring.

i get dropped back into lightdm, losing unsaved data...

really annoying...

Offline

#4 2013-03-30 13:12:27

suare
Member
From: São Paulo, Brazil
Registered: 2013-01-17
Posts: 50

Re: systemd error "File passed too large. Ignoring." How do I fix this?

The same thing is happening with me, sometimes, after my last week update.

Offline

#5 2013-04-05 00:01:02

WST
Member
From: Maykop, RU · Jakarta, ID
Registered: 2013-04-04
Posts: 3
Website

Re: systemd error "File passed too large. Ignoring." How do I fix this?

It happens to me when I kill hanged chromium processes (which seem to be present even if the browser is closed).

Offline

#6 2013-04-05 01:17:44

hadrons123
Member
From: chennai
Registered: 2011-10-07
Posts: 1,249

Re: systemd error "File passed too large. Ignoring." How do I fix this?

Offline

#7 2013-05-13 17:58:39

sinatosk
Member
Registered: 2010-11-28
Posts: 107

Re: systemd error "File passed too large. Ignoring." How do I fix this?

WST wrote:

It happens to me when I kill hanged chromium processes (which seem to be present even if the browser is closed).

thats when I normally see this message

Offline

Board footer

Powered by FluxBB