Problem is excessive logging by the HPLIP software (probably the CUPS backend) in an error case. Forwarding upstream.
To the HP developers, some part of HPLIP, probably the printer I/O part which is used by the "hp" CUPS backend seems to try to access the printer several thousand times per second and on each failure a log message is produced (perhaps one per byte to be sent). This excess of log messages quickly fills up any size of hard disk. If a problem occurs repeatedly, one could perhaps issue one log message and tell how many times the problem repeated. One could also give up or wait some seconds if a certain piece of data sent leads to an error instead of trying to resend it several thousad times per second.
Problem is excessive logging by the HPLIP software (probably the CUPS backend) in an error case. Forwarding upstream.
To the HP developers, some part of HPLIP, probably the printer I/O part which is used by the "hp" CUPS backend seems to try to access the printer several thousand times per second and on each failure a log message is produced (perhaps one per byte to be sent). This excess of log messages quickly fills up any size of hard disk. If a problem occurs repeatedly, one could perhaps issue one log message and tell how many times the problem repeated. One could also give up or wait some seconds if a certain piece of data sent leads to an error instead of trying to resend it several thousad times per second.