diff options
| author | Stephen Hemminger <shemminger@vyatta.com> | 2011-12-02 13:42:56 -0800 |
|---|---|---|
| committer | Stephen Hemminger <shemminger@vyatta.com> | 2011-12-02 13:42:56 -0800 |
| commit | 203f9069f05b38d42ca2969ce1d330b4969c9686 (patch) | |
| tree | 1b3eb7858f576bd5f855132ee8be0da56d8ca4e0 /etc | |
| parent | 49e19e4097942b8c5109061706b7c762c123834b (diff) | |
| download | vyatta-cfg-203f9069f05b38d42ca2969ce1d330b4969c9686.tar.gz vyatta-cfg-203f9069f05b38d42ca2969ce1d330b4969c9686.zip | |
raid: leave modules intact
The RAID startup process is buggy. If modules are unloaded while mdadm
is running it crashes. For now just leave modules intact, and figure
out why MD is unnecessarily started later.
Diffstat (limited to 'etc')
| -rwxr-xr-x | etc/init.d/vyatta-router | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/etc/init.d/vyatta-router b/etc/init.d/vyatta-router index 842481b..70023d0 100755 --- a/etc/init.d/vyatta-router +++ b/etc/init.d/vyatta-router @@ -128,18 +128,6 @@ load_bootfile () ) } - -# Unload the RAID modules that we are not using. It is safe to try to -# unload all of the RAID modules. The kernel will refuse to unload any -# that we are actually using. -# -cleanup_raid() -{ - rmmod raid0 raid1 raid10 raid456 raid6_pq \ - async_raid6_recov async_pq async_xor async_memcpy async_tx \ - linear multipath xor md_mod >/dev/null 2>&1 -} - # # On image booted machines, we need to mount /boot from the image-specific # boot directory so that kernel package installation will put the @@ -227,7 +215,6 @@ start () disabled configure || load_bootfile log_end_msg $? - cleanup_raid telinit q bind_mount_boot chmod g-w,o-w / |