From: Seaman Hu <seaman_hu@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: ext3 fs boot crash [2.4.18-18]
Date: Sun, 8 Sep 2002 19:16:04 -0700 (PDT) [thread overview]
Message-ID: <20020909021604.73867.qmail@web40508.mail.yahoo.com> (raw)
Platform Info:
/dev/sda1 /boot ext3
/dev/sda2 / ext3
Kernel version: 2.4.18-17
Problem:
My system has initrd which contains some modules about
scsi,ext3,etc. During the boot sequence, my system
will crash sometimes(about five times crash once) when
it creates "/boot/kernel.h". Examining fs/namei.c
open_namei(), In failure turn, I found after
path_lookup(), vfs_create() will be called. however,
in vfs_create(), ext2_create() instead of
ext3_create() will be called. While in successful
turn, vfs_create() will not be called.
At the same time, I printed out inode infomation(boot
inode) after path_lookup. "after path_lookup().
nd->dentry->d_inode->i_dev:[256],
nd->dentry->d_inode->i_sb->s_dev:[2049]". here, i_dev:
(1,0) /dev/ram0 while s_dev:(8,1) /dev/sda1. why there
is inconsistent info in inode(boot inode) ?
any comments? thanks very much in advance.
Seaman
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
next reply other threads:[~2002-09-09 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 2:16 Seaman Hu [this message]
2002-09-09 11:08 ` Stephen C. Tweedie
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=20020909021604.73867.qmail@web40508.mail.yahoo.com \
--to=seaman_hu@yahoo.com \
--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
Powered by JetHome