Re: md autostart?
the way i licked this is i took the md entry out of the fstab and after the boot script finishes i have a shell script that performs the filesystem check on the md then mounts it. this works like a charm in our shop. Craig Sanders wrote: >however, this causes problems with 'depmod -a' because the / fs is >still >mounted RO at this time. hmm. if / is still RO at this point, the fsck on root probably failed... m* -- "The Shining One" --
Re: md autostart?
On 26 Mar 1997, Dale Martin wrote: > The only "weird" problem that I have had with it is that I needed to > make sure md and raid0 support were compiled into the kernel and not > "modularized". After doing that, using "mdcreate" to make an mdtab > entry, and adding a line to my fstab, everything started "magically" > working. it works fine as a module IF you edit /etc/init.d/boot and move the stanza which loads the modules & kerneld to just before the stanza which runs 'mdadd -ar' however, this causes problems with 'depmod -a' because the / fs is still mounted RO at this time. craig
Re: md autostart?
Pete Templin <[EMAIL PROTECTED]> writes: > Hi there, > 1) Do I need to do anything to ensure that my /dev/md0 has been started if > I expect to use it in /etc/fstab? If so, where do I put that? My kernel > has md compiled in (not a module). Other people have addressed this question. > 2) Can I also assume that it'll get unmounted cleanly and properly? It does. > Thanks for your help, > > Pete The only "weird" problem that I have had with it is that I needed to make sure md and raid0 support were compiled into the kernel and not "modularized". After doing that, using "mdcreate" to make an mdtab entry, and adding a line to my fstab, everything started "magically" working. I have been using a raid0 partition quite heavily for a few months, and it works very well. Later, Dale -- + finger for pgp public key -+ | Dale E. Martin | University of Cincinnati Savant Research Laboratory | | [EMAIL PROTECTED]| http://www.ececs.uc.edu/~dmartin | +--+
Re: md autostart?
MD setup is easier than it looks. When you used mdcreate to make /dev/md0 it wrote a file called /etc/mdtab. You do not have to modify /etc/init.d/boot since it already has a call to "mdadd -ar" if it and /etc/mdtab exist. In other words, if you are running a recent copy of the sysvinit code and you used mdcreate to make /dev/md0, you probably are already getting it enabled at boot time. Here's what I did to get mine working: # mdcreate raid0 /dev/md0 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde # mdadd -ar # e2fsck -fyv /dev/md0 # mkdir /raid # echo '/dev/md0 /raid ext2 defaults 0 1' >> /etc/fstab # mount /raid # df "cool, it works!" OK, so I hammed it up but you get the idea. Costa Date: Tue, 25 Mar 1997 17:13:30 -0500 (EST) From: Pete Templin <[EMAIL PROTECTED]> To: Debian Users List , debian-devel@lists.debian.org Subject: md autostart? Hi there, I just put the md package to use, and I have some semi-important questions... 1) Do I need to do anything to ensure that my /dev/md0 has been started if I expect to use it in /etc/fstab? If so, where do I put that? My kernel has md compiled in (not a module). 2) Can I also assume that it'll get unmounted cleanly and properly? Thanks for your help, Pete -- Peter J. Templin, Jr. Client Services Analyst Computer & Communication Services tel: (717) 524-1590 Bucknell University [EMAIL PROTECTED]
Re: md autostart?
On Tue, 25 Mar 1997, Pete Templin wrote: > I just put the md package to use, and I have some semi-important > questions... > > 1) Do I need to do anything to ensure that my /dev/md0 has been started if > I expect to use it in /etc/fstab? If so, where do I put that? My kernel > has md compiled in (not a module). > > 2) Can I also assume that it'll get unmounted cleanly and properly? I made it by puting a script into /etc/rc.boot, but I agree mdutils should supply it. (or at least some sort of template) -- - ** Linux ** +---+ ** WAW ** - - [EMAIL PROTECTED] | RENARDIAS Vincent | [EMAIL PROTECTED] - - Debian/GNU Linux +---+ http://www.waw.com/ - - http://www.debian.org/ |WAW (33) 4 91 81 21 45 - - | Luminy (33) 4 91 82 85 32 - ---