I just tried this too. Same result. Anyway, it is 100% replicable here. Can anybody else confirm this? I just did an 1G installation of OpenBSD, then I dd-ed the 1G file (logical block device) to a 100G one. I did all the steps I mentioned above in rescue mode and corrupted the file system.
Nikos On 24 November 2014 at 15:22, Philip Guenther <guent...@gmail.com> wrote: > On Monday, November 24, 2014, Nikos Skalkotos <skalk...@grnet.gr> wrote: >> >> On 23/11/14 06:27, Philip Guenther wrote: >> ... >> > Note the cssize (cylinder summary size) has grown but csaddr hasn't >> > changed. That means it probably had to relocate allocated blocks. This >> > being your root disk, it may have relocated blocks in /boot, which would >> > require re-running installboot. >> >> ... > >> I tried zeroing the space first, and then copying the openbsd image >> into the zeroed space like this: >> > ... > >> But I get the very same error after resizing. I don't think this is it. >> > > Was that with rerunning installboot after the fsck? > > Philip Guenther
