I just saw this in syslog/dmesg: Apr 13 16:15:11 tbox kernel: [15644.272712] Filesystem "dm-3": inode 0x145f0b40 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272724] Filesystem "dm-3": inode 0x145f0b41 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272732] Filesystem "dm-3": inode 0x145f0b42 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272741] Filesystem "dm-3": inode 0x145f0b43 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272749] Filesystem "dm-3": inode 0x145f0b44 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272757] Filesystem "dm-3": inode 0x145f0b45 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272765] Filesystem "dm-3": inode 0x145f0b46 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272773] Filesystem "dm-3": inode 0x145f0b47 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272780] Filesystem "dm-3": inode 0x145f0b48 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272788] Filesystem "dm-3": inode 0x145f0b49 background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272796] Filesystem "dm-3": inode 0x145f0b4a background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272803] Filesystem "dm-3": inode 0x145f0b4b background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272811] Filesystem "dm-3": inode 0x145f0b4c background reclaim flush failed with 11 Apr 13 16:15:11 tbox kernel: [15644.272819] Filesystem "dm-3": inode 0x145f0b4d background reclaim flush failed with 11 Ironically, it happened when I was doing rm -r linux-2.6.34.rc1 to make room for rc4 :P Is this something to worry about? It sounds scary and like a hardware thingy, but smartctl doesn't show anything yet.
Sorry, it's -rc3, not -rc2 Linux tbox 2.6.34-rc3 #1 SMP Wed Mar 31 15:24:34 CEST 2010 x86_64 GNU/Linux
No, it's not serious - it's an EAGAIN error and the code retries later when this happens. The patch to prevent this warning on EAGAIN has not yet made it to the main tree, but should soon.
Just encountered this today: $ dmesg | grep "background reclaim"|wc -l 87 I was doing an 'aptitude full-upgrade' when this happened. If its harmless then all good.
Fix to avoid warning no EAGAIN is in mainline now. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f1d486a3617a2f620b31224e4ace1496c4627e39