From: Andreas Dilger <adilger@turbolabs.com>
To: Hartmut Holz <hartmut.holz@arcormail.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input/output error
Date: Fri, 23 Nov 2001 11:29:47 -0700 [thread overview]
Message-ID: <20011123112947.W1308@lynx.no> (raw)
In-Reply-To: <Pine.LNX.4.33.0111221415490.1518-100000@grignard.amagerkollegiet.dk> <3BFE6E98.8090109@arcormail.de>
In-Reply-To: <3BFE6E98.8090109@arcormail.de>; from hartmut.holz@arcormail.de on Fri, Nov 23, 2001 at 04:43:20PM +0100
On Nov 23, 2001 16:43 +0100, Hartmut Holz wrote:
> 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.
> Entry 'network' in /lock/subsys (30001) has deleted/unused inode 30006.
> Entry 'syslog' in /lock/subsys (30001) has deleted/unused inode 30007.
> Entry 'portmap' in /lock/subsys (30001) has deleted/unused inode 30008.
> Entry 'nfslock' in /lock/subsys (30001) has deleted/unused inode 30009.
> Entry 'syslogd.pid' in /run (38001) has deleted/unused inode 38009.
> Entry 'klogd.pid' in /run (38001) has deleted/unused inode 38010.
I take it that this is after a normal shutdown where you are sure that
the filesystem was unmounted cleanly? It looks like a case where these
files are deleted, but held open by a process.
Could you please try the following:
- "telinit 1" to change into single user mode
- make sure all of the above processes are stopped (check via ps, and
"/etc/rc.d/init.d/foo stop" for each one
- "lsof | grep /var" to see if any files are still open on /var
- umount /var
- e2fsck -f /dev/hdX
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-23 18:30 UTC|newest]
Thread overview: 18+ 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
2001-11-23 18:29 ` Andreas Dilger [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 14:06 Kenneth Johansson
2003-03-07 16:37 input/output error Brent Clements
2003-03-07 17:00 ` Trond Myklebust
2011-02-22 15:44 Input/Output error Srinivasan T
2011-02-22 20:21 ` Eric Sandeen
2011-02-23 6:33 ` Srinivasan T
2011-02-23 16:32 ` Eric Sandeen
2011-02-23 21:55 ` Dave Chinner
2011-02-23 0:47 ` Dave Chinner
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=20011123112947.W1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.