knitti wrote:
On 11/14/07, Clint Pachl <[EMAIL PROTECTED]> wrote:
knitti wrote:
Instead of e.g. /dev/sd0a try /dev/rsd0a. I didn't try with svnd, but
when copying partitions with dd I use this.
I tried that, but like I said fdisk complained when the svnd device is
associated with the raw direct access disk device. For example
# vnconfig -k svnd0 /dev/rwd1c
# fdisk -c 19457 -h 255 -s 63 -i svnd0 # disk CHS
fdisk: error initializing MBR: bad address
# fdisk -c 19456 -h 254 -s 63 -i svnd0 # OpenBSD partition CHS
fdisk: error initializing MBR: bad address
# fdisk -i svnd0
Warning CHS values out of bounds only saving LBA values
fdisk: error initializing MBR: bad address
well, the 'c' slice is a bit 'special', perhaps try an 'a' slice filling the
whole disk but the first track? After all, I think its weird not to have
an MBR etc. on the real disk. (Which doesn't mean that I couldn't
imagine that).
I understand that the "c" partition is special. But when the entire disk
(i.e. wd0c) is just acting as a storage backend and the svnd device is
the front end, I don't think it matters. It's not like I'm going to be
running newfs or fsck on the actual disk. Anyway, I have tried on the
"a" partition too, but I get the same results.
Like I said, everything works fine if I use the buffered device,
wd0[ac], not rwd0[ac], but it is so slow. dd'ing to the unbuffered
device is much faster than dd'ing to the buffered. That is why I thought
I would try to associate the svnd device with the unbuffered disk device.
Thanks for you input.
