From: David Brownell <david-b@pacbell.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [path 2.6] reduce ext3 log spamming (blank lines)
Date: Tue, 7 Dec 2004 15:01:15 -0800 [thread overview]
Message-ID: <200412071501.15815.david-b@pacbell.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]
When drives go offline, e.g. usb-storage disconnect, the
upper layers don't behave very intelligently yet: ext3
over scsi keeps retrying reads, logging three lines for
each error:
10:58:31 scsi0 (0:0): rejecting I/O to dead device
10:58:31 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:58:31
10:58:55 scsi0 (0:0): rejecting I/O to dead device
10:58:55 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:58:55
10:59:30 scsi0 (0:0): rejecting I/O to dead device
10:59:30 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:30
10:59:30 scsi0 (0:0): rejecting I/O to dead device
10:59:30 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:30
10:59:30 scsi0 (0:0): rejecting I/O to dead device
10:59:30 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:30
10:59:32 scsi0 (0:0): rejecting I/O to dead device
10:59:32 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:32
10:59:32 scsi0 (0:0): rejecting I/O to dead device
10:59:32 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:32
10:59:33 scsi0 (0:0): rejecting I/O to dead device
10:59:33 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:33
10:59:47 scsi0 (0:0): rejecting I/O to dead device
10:59:47 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:47
10:59:48 scsi0 (0:0): rejecting I/O to dead device
10:59:48 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:48
10:59:49 scsi0 (0:0): rejecting I/O to dead device
10:59:49 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
10:59:49
11:00:07 scsi0 (0:0): rejecting I/O to dead device
11:00:07 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0
11:00:07
This patch shrinks that log spam by the trivial third, getting
rid of those needless blank lines. It's not clear to me why
the "no such device" errors don't immediately make ext3
(or is it the block layer?) give up ... maybe someone else
can make Linux not retry after those errors.
- Dave
[-- Attachment #2: ext3.patch --]
[-- Type: text/x-diff, Size: 581 bytes --]
Prevent one ext3 error report from spamming dmesg/syslog with blank lines;
ext3_error() already includes the necessary newline.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
--- 1.59/fs/ext3/namei.c Tue Oct 19 02:40:30 2004
+++ edited/fs/ext3/namei.c Tue Dec 7 14:28:10 2004
@@ -872,7 +872,7 @@
if (!buffer_uptodate(bh)) {
/* read error, skip block & hope for the best */
ext3_error(sb, __FUNCTION__, "reading directory #%lu "
- "offset %lu\n", dir->i_ino, block);
+ "offset %lu", dir->i_ino, block);
brelse(bh);
goto next;
}
next reply other threads:[~2004-12-07 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 23:01 David Brownell [this message]
2004-12-08 5:58 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412071501.15815.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome