On Tue, 19 Apr 2011, 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.
The disklabel of the disk is located at the very beginning of the disk (or
at the beginning of an fdisk partition on some archs), that means at the
beginning of the physically first partition. This partition usually is the
'a' partition. If you overwrite the beginning of the first partition, you
overwrite the disklabel.
On the other hand, if you overwrite disklabel area of any of the following
partitions (structured as FFS), like wd0l, you usually cause no harm. It
is not used there.
As for svnd, if I remeber it right, you should not use a partition for
svnd, but a file instead. But don't know why it is necessary.
Regards,
David
