From: Walter Hofmann <walter.hofmann@physik.stud.uni-erlangen.de>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18/ext2: special file corruption?
Date: Mon, 26 Feb 2001 18:16:34 +0100 [thread overview]
Message-ID: <20010226181634.A5097@frodo.uni-erlangen.de> (raw)
In-Reply-To: <3A9A2E3D.9135.8E1BCE@localhost>
In-Reply-To: <3A9A2E3D.9135.8E1BCE@localhost>; from Ulrich.Windl@rz.uni-regensburg.de on Mon, Feb 26, 2001 at 10:21:51AM +0100
Ulrich Windl schrieb am Montag, den 26. Februar 2001:
> 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."
I see them too on every fsck (after a crash). I'm using e2fsck 1.19 (but
not from SuSE. The rpm was built on snap.thunk.org, but I can't
remember where I got it from).
Walter
next prev parent reply other threads:[~2001-02-26 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 9:21 2.2.18/ext2: special file corruption? Ulrich Windl
2001-02-26 17:16 ` Walter Hofmann [this message]
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=20010226181634.A5097@frodo.uni-erlangen.de \
--to=walter.hofmann@physik.stud.uni-erlangen.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).