On Wed, Jan 5, 2011 at 1:16 PM, Cindy Swearingen <cindy.swearin...@oracle.com> wrote: > You might review your zpool history -il rpool output for clues.
This isn't a critical problem, it's just a point of annoyance since it seems like something that shouldn't happen. It's also just a test host that's led a hard life full of abuse and hardware swaps. I'm not sure where to start looking in the history output. The pool was created with snv_125 and upgraded to snv_133 when that became available. It's been around for a bit over a year. There were some failed upgrades from snv_134b to snv_151a. The devices shown under 'zpool status' were different than the actual devices in use, because they'd been moved to a new controller at some point. After fixing that, the upgrade succeeded. It's possible that something broke down during the many hoops that had to be jumped through however. I can mail you the send stream from rp...@copy if you think it would help to find the problem. There's no priority to fixing it, other than it being something weird that shouldn't have happened. -B -- Brandon High : bh...@freaks.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
