I was also hit by this bug. The rate of logspam caused by the failure message was so intense that my laptop's SATA SSD was filling up at hundreds of MiB per minute. The I/O flood made everything slow down; login barely worked, bash-completion tabbing took 5-10 s, and figuring out which process(es) to kill before space runs out was a race against time that I nearly lost.
It's been a long time since I last experienced a bug that demanded a similarly urgent and decisive user response as this. In my opinion this is a serious one.
