On Wed, Feb 17, 2010 at 16:25, Daniel Carosone <d...@geek.com.au> wrote:
> On Thu, Feb 18, 2010 at 08:14:03AM +1100, Daniel Carosone wrote: > > I think > > you probably want to make a slice 0 that spans the right disk sectors. > [..] > > you could try zdb -l on /dev/dsk/c...p[01234] as well. > > Depending on how and what you copied, you may have zfs data that start > at sector 0, with no space for any partitioning labels at all. If > zdb -l /dev/rdsk/c..p0 shows a full set, this is what has happened. > Trying to write partition tables may overwrite some of the zfs labels. > > zfs won't import such a pool by default (it doesn't check those > devices). You could cheat, by making a directory with symlinks to the > p0 devices, and using import -d, but this will not work at boot. It > would be a way to verify current state, so you can then plan next > steps. > > -- > Dan. > It looks like using p0 is exactly what I want, actually. Are s2 and p0 both the entire disk? The idea of symlinking to the full-disk devices from a directory and using -d had crossed my mind, but I wasn't sure about it. I think that is something worth trying. I'm not too concerned about it not working at boot - I just want to get something working at all, at the moment. -Ethan
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
