On Tue, 15 Dec 1998, Tom Brown wrote:
> raid0145-19981214-2.0.36.gz
> raidtools-19981214-0.90.tar.gz
>
> 4 x 10 gig maxtor IDE drives...
>
> I can't seem to do anything with my hdc1 partition.... I keep getting:
>
> fs_may_mount: found busy/dirty/locked inode: device 00:00, inode 116,
> mode=00000000, count=1, i_dirt=0, i_lock=0
>
> md: can not import hdc1, has active inodes!
> could not import hdc1!
> autostart hdc1 failed!
>
>
> the fs_may_mount line is my hack to the kernel...
>
> I dropped the partition, and used the tracks as hdc... I also rewrote
> /etc/raidtab to call it md3 instead of md0 ... and now raidstart seems to
> have succeeded...
>
> I really don't understand what was going on... I went through multiple
> reboots while trying to figure this out...
>
> It MIGHT be significant that a rebuild on md1 kept getting triggered, it's
> 27 gig so it never got a chance to finish...
>
> ... Not sure what else I can say/provide...
>
> -Tom
hhmm... why does it never fail that as soon as one hits send, one finds
the problem... (or at least more important evidence).
md: serializing resync, md1 has overlapping physical units with md3!
hdd2 [events: 00000012](write) hdd2's sb offset: 9055296
hdb2 [events: 00000012](write) hdb2's sb offset: 9055296
hda6 [events: 00000012](write) hda6's sb offset: 9055232
----------
Disk /dev/hdc: 16 heads, 63 sectors, 19390 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Begin Start End Blocks Id System
/dev/hdc2 1024 1424 19390 9055368 83 Linux native
/dev/hdc3 1 1 1423 717160+ 83 Linux native
The number of cylinders for this disk is set to 19390.
I never understood the difference between begin and start... I still
don't... if I define the partitions from the start of the disk, then they
are accepted, if I delete and try to recreate hdc3 as shown, fdisk won't
let me... sigh...
