From: "Chris Evans" <chris1@psyctc.org>
To: 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 09:11:48 -0000 [thread overview]
Message-ID: <4045A154.12266.4B21C5B@localhost> (raw)
In-Reply-To: <16453.13250.331087.281490@notabene.cse.unsw.edu.au>
I'm splitting my response to this post into two. I'm sure that
someone out there who knows about mount and /proc/mounts can clarify
this bit:
On 3 Mar 2004 at 12:24, Neil Brown wrote:
> On Wednesday March 3, chris1@psyctc.org wrote:
> > Aha, didn't know that wrinkle: lovely. Mount says:
> > /dev/md0 on / type ext3 (rw,errors=remount-ro)
> > proc on /proc type proc (rw)
> > devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> >
> > and cat /proc/mounts says:
> > rootfs / rootfs rw 0 0
> > /dev/root / ext2 rw 0 0
> > proc /proc proc rw 0 0
> > devpts /dev/pts devpts rw 0 0
> >
> > Does that "/dev/root" bit indicate anything useful?
>
> No, but the fact that root is actually 'ext2' even though mount (and
> presumably fstab) thinks it is ext3 is a bit suspicious.
I suppose that might be because the difference between ext2 and ext3,
as I understand it, is just a journalling block reserved at the end
of the normal ext2 space so perhaps /proc/mounts indicates all ext3
as ext2?
From a quick bit of googling, I understand that /dev/root is a label
for the root mount point that's passed to the kernel as it loads, in
my case, I assume that's passed to the kernel from whatever lilo has
done to the mbr and that this ensures that the kernel then holds that
mount open (presumably in case it needs to write something back there
when it quits ... or perhaps it always writes something back there in
a clean dismount ... I don't know).
Can someone:
a) confirm or deny my hunch that the ext2/ext3 issue is normal?
b) clarify the way that lilo and the kernel interact?
I wonder if it's pertinent that /proc/partitions shows this:
cat /proc/partitions
major minor #blocks name
9 0 78124928 md0
22 0 80043264 hdc
22 1 78125008 hdc1
3 64 80043264 hdb
3 65 80035798 hdb1
cfdisk /dev/hdb shows a single primary bootable partition occupying
the entire drive of Linux raid autodetect type. For /dev/hdc I have
a single primary bootable partition of the same type and some free
space (to ensure that there'd be enough room on /dev/hdb1 to add it
to the array).
Thanks,
Chris
PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling
and Therapeutic Communities; practice, research,
teaching and consultancy.
Chris Evans & Jo-anne Carlyle
http://psyctc.org/ Email: chris@psyctc.org
next prev parent reply other threads:[~2004-03-03 9:11 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 [this message]
2004-03-03 15:36 ` Paul Clements
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=4045A154.12266.4B21C5B@localhost \
--to=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).