In article <juk971$qpi$1...@serpens.de>, Michael van Elst <mlel...@serpens.de> wrote: >e...@math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=) writes: > >>> It probably won't help you with raidframe. >>It would indeed help in my case. In case sd6 has gone missing, so dk4 >is on the RAID and not on sd6, it would prevent the wrong filesystem >being mounted for dk5. > >I was refering to the situation with building a raid on wedge components. >Wedges on top of raid are no problem.
Actually I do exactly that (raid on top of wedges) dk0 at wd0: wd0a dk0: 488397105 blocks at 63, type: raidframe dk1 at wd1: wd1a dk1: 488397105 blocks at 63, type: raidframe dk2 at sd0: sd0a dk2: 117210177 blocks at 63, type: ffs Component on: dk0: 488397105 Component on: dk1: 488397105 Found: dk1 at 0 Found: dk1 at 0 Found(low mod_counter): dk0 at 1 raid0: Components: /dev/dk1 /dev/dk0[**FAILED**] Ignore the failed dk here, this is because of the bad ata code in current. In fstab I have: NAME=raid0a / ffs rw,log 7 1 NAME=raid0b none swap sw 0 0 NAME=raid0e /var ffs rw,log 7 3 NAME=raid0f /usr ffs rw,log 7 3 NAME=raid0g /usr/local ffs rw,log 7 3 .... christos