linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: Chris Evans <chris1@psyctc.org>
Cc: debian-user@lists.debian.org, linux-raid@vger.kernel.org
Subject: Re: md: can not impport hdb1, has active inodes!
Date: Wed, 03 Mar 2004 10:36:15 -0500	[thread overview]
Message-ID: <4045FB6F.7D934181@SteelEye.com> (raw)
In-Reply-To: 4045A154.12266.4B21C5B@localhost

Chris Evans wrote:

> a) confirm or deny my hunch that the ext2/ext3 issue is normal?

A reasonable hunch, but no, it is not normal for an ext3 root fs to show
up as ext2 in /proc/mounts:

# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw 0 0
/proc /proc proc rw 0 0
[snip]

Perhaps you don't have ext3 support built in to the kernel? If not,
you'll need an initrd to boot your root fs as ext3.


As far as the active inodes on /dev/hdb1, one thing you might try is:

fuser -vm /dev/hdb1

If there's a process accessing /dev/hdb1, it will be listed.

--
Paul

  reply	other threads:[~2004-03-03 15:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 22:17 md: can not impport hdb1, has active inodes! Chris Evans
2004-03-02 23:24 ` Cameron Moore
2004-03-03  0:36   ` Chris Evans
2004-03-02 23:40 ` Neil Brown
2004-03-03  0:36   ` Chris Evans
2004-03-03  1:04     ` Neil Brown
2004-03-03  1:13       ` Chris Evans
2004-03-03  1:24         ` Neil Brown
2004-03-03  9:11           ` Chris Evans
2004-03-03 15:36             ` Paul Clements [this message]
2004-03-04 18:56               ` Juri Haberland
2004-03-03  1:11     ` Maarten J H van den Berg
2004-03-03  1:20       ` Chris Evans
2004-03-03  2:36         ` Maarten J H van den Berg
2004-03-03 16:54           ` Chris Evans
     [not found]             ` <200403031109.17348.jguerin@cso.atmel.com>
2004-03-03 22:09               ` Chris Evans
2004-03-04  2:08             ` Maarten J H van den Berg

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=4045FB6F.7D934181@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=chris1@psyctc.org \
    --cc=debian-user@lists.debian.org \
    --cc=linux-raid@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).