From: "Chris Evans" <chris1@psyctc.org>
To: linux-raid@vger.kernel.org
Subject: md: can not impport hdb1, has active inodes!
Date: Tue, 02 Mar 2004 22:17:08 -0000 [thread overview]
Message-ID: <404507E4.8552.25AC3E6@localhost> (raw)
Debian stable 2.4.19 kernel with RAID1 compiled in, VIA EPIA CL1000
motherboard, 2 Maxtor DiamondMax 9 7200rpm 80Gb drives as /dev/hdb
and /dev/hdc from onboard controller.
I've followed the guide at:
http://www.cs.montana.edu/faq/faqw.admin.py?query=Convert+Root+System+
to+Software+Raid&querytype=simple&casefold=yes&req=search
which had turned up on a debian list search to try to set up the
RAID1 mirror of the boot/root drive. I installed to /dev/hdb1
(/dev/hda is the CDROM and perhaps I should have changed that first).
Loaded 2.2.20, got 2.4.19 sources, compiled RAID1 support into the
kernel (still can't get rid of one complaint about a missing
character set module but don't think that's causing any real
problems), made the identical /dev/hdc1 into a somewhat smaller linux
autodetect RAID format partition, mounted it as 2nd drive in a RAID1
drive using:
mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/hdc1
which worked fine, mkfs -t ext3 /dev/hdc1, mount it to /mnt1,
cp -ax / /mnt, tweak /etc/fstab ... /dev/md0 mounts fine, tweak lilo
conf to boot from /dev/md0, reboot -- fine, finally come to add
/dev/hdb1 into the array after resetting the partition type to
autodetect RAID ...
.. no go, system complains that /dev/hdb1 is mounted or that an inode
is active:
md: can not impport hdb1, has active inodes!
md: error, md_import_device() returned -16
I assume that's because the boot is still from /dev/hdb but if so,
how come the howto says this should work. Seems that nothing I do
can shift this and if I set the partition back to linux I find I
can't mount the drive despite rebooting as I get:
mount: /dev/hdb1 already mounted or /mnt1 busy
/mnt1 isn't busy (I can create a completely new mount point: no
difference) and mount shows that /dev/hdb1 isn't mounted.
I've tried all sorts of tweaking with lilo.conf to remove any calls
to /dev/hdb but either these don't change anything, or else lilo
complains that it can't install to the target (e.g. /dev/md0).
I've read through the docs and man pages and done some
searching around but can't find any explanations.
Help of any sort, including direct pointers to what I've missed or
misread, desperately needed!
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 reply other threads:[~2004-03-02 22:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 22:17 Chris Evans [this message]
2004-03-02 23:24 ` md: can not impport hdb1, has active inodes! 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
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=404507E4.8552.25AC3E6@localhost \
--to=chris1@psyctc.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).