linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: 2.2.18/ext2: special file corruption?
Date: Mon, 26 Feb 2001 10:21:51 +0100	[thread overview]
Message-ID: <3A9A2E3D.9135.8E1BCE@localhost> (raw)

Hi,

I had an interesting effect: Due to NVdriver I had a lot of system 
freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the 
message that one specific "Special (device/socket/fifo) inode .. has 
non-zero size. FIXED."

Interestingly I got the message for every reboot. So either the kernel 
corrupts the very same inode every time, or e2fsck does not really fix 
it, or the error simply doesn't exist. I think the kernel doesn't 
temporarily set the size to non-zero, so this seems strange.

Regards,
Ulrich


             reply	other threads:[~2001-02-26 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26  9:21 Ulrich Windl [this message]
2001-02-26 17:16 ` 2.2.18/ext2: special file corruption? Walter Hofmann
2001-02-26 17:48 ` Andreas Dilger
2001-02-27  6:53 ` Ulrich Windl

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=3A9A2E3D.9135.8E1BCE@localhost \
    --to=ulrich.windl@rz.uni-regensburg.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;
as well as URLs for NNTP newsgroup(s).