Re: mdadm size and raid1 on unslung 6
- Unless you want to boot from a raid partition, then there is no need
to copy mdadm into initrd.
On my system I boot from a normal partition and then mount the raid
partition and export it as a samba share later in the boot process.
--- In firstname.lastname@example.org, Brond Larson <brondl@...> wrote:
> I'm following the howto for raid 1 on unslung6, and I'm aware of the
> new howto script
> (at http://www.nslu2-linux.org/wiki/HowTo/Raid1onUnslung6 ), but even
> with that
> I'm seeing a big discrepancy between the reported size of the mdadm
> binary and what
> 'ipkg install mdadm' gives me.
> The howto gives this listing:
> # ls -l /initrd/unslung
> -rw-rw-r-- 1 root root 53392 Jul 19 22:15 md.o
> -rwxrwxr-x 1 root root 121368 Jul 19 22:15 mdadm
> -rw-rw-r-- 1 root root 20192 Jul 19 22:15 raid1.o
> Whereas the installed mdadm binary I get is almost 2x larger:
> ls -al /opt/sbin/mdadm
> -rwxrwxr-x 1 root root 280812 Jun 21 2007 /opt/sbin/mdadm
> I don't think the howto procedure will work with an mdadm of this
> size. I run out
> of space trying to copy it to /initrd/unslung. Even after removing /
> and quotaon (as suggested in http://tech.groups.yahoo.com/group/nslu2-
> df shows less than 100k remaining, which I'm guessing will be too
> little to boot succesfully (though
> I have not tried it).
> What changed with mdadm? If this is a recent version change in
> mdadm, are older versions