On Tue, Apr 19, 2011 at 08:47:03PM +0000, Kevin Chadwick wrote:
> On Tue, 19 Apr 2011 10:18:20 +0000
> Kevin Chadwick wrote:
> 
> >  /sbin/disklabel -E wd1
> >  /sbin/vnconfig -ck svnd0 /dev/wd1a
> >  /sbin/disklabel -E svnd0
> >  /sbin/newfs /dev/rsvnd0a
> >  /sbin/newfs /dev/rsvnd0d
> >  
> >  /sbin/disklabel -E wd0
> >  /sbin/vnconfig -ck svnd1 /dev/wd0l
> >  /sbin/disklabel -E svnd1
> >  /sbin/newfs /dev/rsvnd1a
> >  
> >  reboot, I guess disklabel -c would do the same
> >  
> >  wd0l and svnd1 work fine (disklabels visible and work fine)
> >  
> >  I have to recreate the disklabel for wd1 and svnd0 after which it works
> >  fine untill the next reboot (data accessed).
> 
> Anyone got even a hunch why wd1a and wd0l as used above behave
> repeatably differently. 
> 

Are you sure you can use /dev/wd1a as backend file for a vnd? From my
understanding block devices should not be used for anything that does file
IO. So have you tried /dev/rwd1a instead in the vnconfig command?

-- 
:wq Claudio

Reply via email to