From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: init_special_inode: bogus imode (37316) means ?
Date: Wed, 21 Jul 2004 15:51:25 -0700 [thread overview]
Message-ID: <1090450285.21477.4.camel@heat> (raw)
This useless error popped up in dmesg today on a 2.4.26 SMP x86 host:
EXT2-fs: corrupt root inode, run e2fsck
init_special_inode: bogus imode (37316)
EXT2-fs: corrupt root inode, run e2fsck
init_special_inode: bogus imode (37316)
EXT2-fs: corrupt root inode, run e2fsck
Well that's great, thanks. What device are we talking about? Should I
be worried about my data? None of the storage devices show any errors,
although the machine has been under extreme I/O load for over a week.
This particular host has one internal PATA disk (WDC WD1200JB) attached
via AMD-8111 IDE (rev 03) with an ext2 fs, and two raids of four SATA
disks each, attached via 3Ware controller. Each RAID has an ext3 fs.
Any advice about how to proceed would be appreciated.
-jwb
reply other threads:[~2004-07-21 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1090450285.21477.4.camel@heat \
--to=jwbaker@acm.org \
--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