From: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: kernel log messages and disk space
Date: Sun, 21 Aug 2005 09:52:22 -0700 [thread overview]
Message-ID: <4308B146.8040203@comarre.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0508201812550.24204-100000@treebeard.engin.umich.edu>
Karthik Vishwanath wrote:
> Hello,
>
> Observed today, that my machine had utilized ~ 7G of hard drive space
> (since the last time I saw it, ~ week ago)! The real killers were:
>
> # du -hcs /var/log/* | grep -E '^[0-9]*.[0-9]*G'
> 2.6G /var/log/kern.log.0
> 2.6G /var/log/messages.0
> 2.6G /var/log/syslog.0
>
> On inspection each of these files along with the /var/log/messages,
> /var/log/kern.log and /var/log/syslog, contained messages as pasted below.
> Am pasting the contents near the head/tail of each of these files (just to
> highlight that the sector-numbers/time-stamps of these messages were quite
> varied, and that these messages were repeated over and over again till the
> filesize grew to what du showed).
>
> I would much appreciate any input on what is/was causing this behavior,
> and, how I may be able to catch it/fix it, therefore.
Wel, device 03:01 is /dev/hda1, and this time (I mean in contrast to
James' recent posting) the reports do sound like an emerging hardware
failure, especially if you are getting this many of them. So you *may*
need a new hard disk.
But first, let's consider other possibilities ... the one I think of is
a combination of a partitioning error and a drive that is nearly full
(so the error is just now becoming visiale). Either you or we should
look at this information:
output of "df"
the drive's partition table (as reported by fdisk, say).
the physical size of the drive (as reported in dmesg during boot/init,
preferably)
Another possibility is a bad spot in RAM. So let's look at:
output of "free" (both lines) run proximate to the messages in the logs.
Finally ... is this system doing anything special that involves frequent
access to the hard disk? If so, what?
I'm assuming you'd have mentioned any recent changes (a kernel upgrade
is the most obvious) associated with this problem, so I'm not
considering that sort of cause.
>
> The file contents follow:
>
> [# tail -n3 /var/log/kern.log.0]
>
> Aug 18 07:38:18 mithrandir kernel: attempt to access beyond end of device
> Aug 18 07:38:18 mithrandir kernel: 03:01: rw=0, want=2031123176,
> limit=13277691
> Aug 18 07:38:18 mithrandir kernel: attempt to access beyond end of device
>
>
> [# tail -n3 var/log/messages]
> Aug 20 07:38:23 mithrandir kernel: attempt to access beyond end of device
> Aug 20 07:38:23 mithrandir kernel: 03:01: rw=0, want=1373859054,
> limit=13277691
> Aug 20 07:38:23 mithrandir kernel: Directory sread (sector 0xa3c6d9dc)
> failed
>
> [# tail -n3 /var/log/syslog]
>
> Aug 20 08:41:13 mithrandir kernel: attempt to access beyond end of device
> Aug 20 08:41:13 mithrandir kernel: 03:01: rw=0, want=71196829,
> limit=13277691
> Aug 20 08:41:13 mithrandir kernel: Directory sread (sector 0x87cc13a)
> failed
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-08-21 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 22:34 kernel log messages and disk space Karthik Vishwanath
2005-08-21 16:52 ` Ray Olszewski [this message]
2005-09-01 23:54 ` Karthik Vishwanath
[not found] <Pine.LNX.4.44.0509012049410.4730-100000@treebeard.engin.umich.edu>
2005-09-02 1:50 ` Ray Olszewski
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=4308B146.8040203@comarre.com \
--to=ray@comarre.com \
--cc=linux-newbie@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