From: Hartmut Holz <hartmut.holz@arcormail.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Input/output error
Date: Fri, 23 Nov 2001 16:43:20 +0100 [thread overview]
Message-ID: <3BFE6E98.8090109@arcormail.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0111221415490.1518-100000@grignard.amagerkollegiet.dk>
Rasmus Bøg Hansen wrote:
> On Thu, 22 Nov 2001, Marcus Grando wrote:
>
>
>>On try start syslog deamon occur this errrors "Input/output error" on many archives /var directory.
>>
>
> Try to run fsck on the /var partition. Also you should check the disk
> for bad blocks. What output do you get from the kernel ('dmesg',
> /var/log/messages etc.)?
>
> It could be a bad disk developing bad sectors.
>
> Rasmus
>
>
On my machine (2.4.15 final) it is the same behaviour. After reboot
the lock files (and only the lock files) are corrupt. With 2.4.14 and
2.4.13 everything works fine. gcc 2.96, e2fsck 1.25, aic7896/97
e2fsck output:
--------------
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'kudzu' in /lock/subsys (30001) has deleted/unused inode 30005.
Clear? yes
Entry 'network' in /lock/subsys (30001) has deleted/unused inode 30006.
Clear? yes
Entry 'syslog' in /lock/subsys (30001) has deleted/unused inode 30007.
Clear? yes
Entry 'portmap' in /lock/subsys (30001) has deleted/unused inode 30008.
Clear? yes
Entry 'nfslock' in /lock/subsys (30001) has deleted/unused inode 30009.
Clear? yes
Entry 'random' in /lock/subsys (30001) has deleted/unused inode 30012.
Clear? yes
Entry 'netfs' in /lock/subsys (30001) has deleted/unused inode 30013.
Clear? yes
Entry 'autofs' in /lock/subsys (30001) has deleted/unused inode 30014.
Clear? yes
Entry 'local' in /lock/subsys (30001) has deleted/unused inode 30029.
Clear? yes
Entry 'syslogd.pid' in /run (38001) has deleted/unused inode 38009.
Clear? yes
Entry 'klogd.pid' in /run (38001) has deleted/unused inode 38010.
Clear? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/var: ***** FILE SYSTEM WAS MODIFIED *****
/var: 23017/66000 files (5.9% non-contiguous), 115364/263168 blocks
next prev parent reply other threads:[~2001-11-23 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 13:04 Input/output error Marcus Grando
2001-11-22 13:17 ` Rasmus Bøg Hansen
2001-11-23 15:43 ` Hartmut Holz [this message]
2001-11-23 18:29 ` Andreas Dilger
2001-11-23 18:50 ` Marcus Grando
2001-11-23 20:20 ` Hartmut Holz
2001-11-23 19:10 ` Tom Eastep
2001-11-25 22:50 ` Horst von Brand
2001-11-26 0:05 ` Russell King
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=3BFE6E98.8090109@arcormail.de \
--to=hartmut.holz@arcormail.de \
--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