I just noticed that my previous assessment was not quite accurate. It's
even stranger. Let's try again.
On S10/b101, I have two pools:
zpool list
NAME SIZE USED AVAILCAP HEALTH ALTROOT
double 172G 116G 56.3G67% ONLINE -
single 516G 61.3G 455G11% ONLINE -
double is mirrored. single is not. single has the following datasets:
zfs list -r single
NAME USED AVAIL REFER MOUNTPOINT
single 61.3G 447G 1.50K none
single/backup 1.55G 447G 1.93M /export/storage
single/backup/cari18K 447G18K /export/home/cari/storage
single/backup/dant 1.54G 447G 1.54G /export/home/dant/storage
single/misc 54.0G 447G 24.5K none
single/misc/dant54.0G 447G 24.5K none
single/misc/dant/music 38.1G 447G 38.1G /export/home/dant/Music
single/misc/dant/vbox 15.9G 447G 15.9G /export/home/dant/VMs
single/share 18K 447G18K /export/share
single/software 5.73G 447G 5.73G /usr/local
After doing a zpool import from b104, I have:
zpool list
NAME SIZE USED AVAILCAP HEALTH ALTROOT
double 516G 61.3G 455G11% ONLINE -
and zpool import -D shows me that single is unavailable because it's
corrupted because zpool thinks it's on the wrong partition. Same as
what I wrote before. What I didn't notice before was a subtle
difference in the zpool list. It's more obvious if we look at the zfs list:
zfs list
NAME USED AVAIL REFER MOUNTPOINT
double 61.3G 447G 1.50K none
double/backup 1.55G 447G 1.93M /export/storage
double/backup/cari18K 447G18K /export/home/cari/storage
double/backup/dant 1.54G 447G 1.54G /export/home/dant/storage
double/misc 54.0G 447G 24.5K none
double/misc/dant54.0G 447G 24.5K none
double/misc/dant/music 38.1G 447G 38.1G /export/home/dant/Music
double/misc/dant/vbox 15.9G 447G 15.9G /export/home/dant/VMs
double/share 18K 447G18K /export/share
double/software 5.73G 447G 5.73G /usr/local
Notice that those are the datasets from single on b101! So, not only
does b104 have the location of the single pool wrong, but it thinks the
double pool is where the single pool is. WTF?
Daniel
Daniel Templeton wrote:
Hi!
I have a system with S10, b101, and b104 installed in the same
partition on disk 1. On disks 1 and 2 in different partitions, I also
created ZFS pools from S10 to be imported by b101 and b104. Pool 1 is
mirrored. Pool 2 is not. About every three builds, I replace the
oldest build with the latest available and switch to that as the
default OS. Up through 101 everything was fine. I just installed
104, however, and when I do the zpool import, the mirrored pool is
picked up just fine, but the non-mirrored pool shows up as corrupted.
zpool import -D shows me that zpool on b104 thinks that the pool is on
c1t1d0p2, whereas S10, b101, and fdisk agree that it's actually on
c1t1d0p3. How do I convince zpool on b104 where my non-mirrored pool
really is? I'm a bit afraid to do an import -f because that pool is
my home directory, and I'd really rather not screw it up. And I don't
see where the -f will change zpool's mind about where the pool
actually lives. Maybe import -c from the default location? Where is
the default location? Any thoughts or suggestions?
Thanks!
Daniel
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
