Are 1.7.1 new pools compatible with 1.5.2?
Posted: Wed Mar 14, 2018 2:04 am
Hi!
Thanks for the long-awaited update!
The issue I had on Mavericks with v1.6.1 seems gone.
(https://openzfsonosx.org/forum/viewtopic.php?f=15&t=3012)
At least as long as I boot in my test OS 10.9.5 where I installed 1.7.1...
When I boot back to my main system (still running 1.5.2):
- the first pool I created with 1.7.1 (boldly named Test ) is not imported and the underlying HFS partition (named ZFS1) is mounted instead.
- the Console gets filled with so many of those lines:
If I eject ZFS1 and import Test, I see the few files I dropped there under 1.7.1 and zpool status shows:
The strangest thing is that the second pool I created together with the first one automounts without issue and its zpool status shows "No known data errors".
So, before I try the move to 1.7.1 on all my OSes,I need to know if there should be a compatibility of the new pools or if this is normal behavior?
Especially if I upgrade my pools, there'll probably be no turning back...
On the good side, my old pools don't seem affected at all and mount correctly on both versions.
Thanks for the long-awaited update!
The issue I had on Mavericks with v1.6.1 seems gone.
(https://openzfsonosx.org/forum/viewtopic.php?f=15&t=3012)
At least as long as I boot in my test OS 10.9.5 where I installed 1.7.1...
When I boot back to my main system (still running 1.5.2):
- the first pool I created with 1.7.1 (boldly named Test ) is not imported and the underlying HFS partition (named ZFS1) is mounted instead.
- the Console gets filled with so many of those lines:
- Code: Select all
14/03/18 10:19:47,000 kernel[0]: hfs: BlockMarkFreeInternal() trying to free unallocated blocks on volume ZFS1
14/03/18 10:19:47,000 kernel[0]: hfs: Runtime corruption detected on ZFS1, fsck will be forced on next mount.
If I eject ZFS1 and import Test, I see the few files I dropped there under 1.7.1 and zpool status shows:
- Code: Select all
pool: Test
state: ONLINE
status: One or more devices has experienced an error resulting in data corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the entire pool from backup.
see: http://zfsonlinux.org/msg/ZFS-8000-8A
scan: none requested
config:
NAME STATE READ WRITE CKSUM
Test ONLINE 0 0 4
volume-65714D12-064E-3A8D-A56D-676C625471EA ONLINE 0 0 15
errors: Permanent errors have been detected in the following files:
/Volumes/Test/.VolumeIcon.icns
/Volumes/Test/.Spotlight-V100/Store-V1/VolumeConfig.plist
/Volumes/Test/.Spotlight-V100/VolumeConfiguration.plist
The strangest thing is that the second pool I created together with the first one automounts without issue and its zpool status shows "No known data errors".
So, before I try the move to 1.7.1 on all my OSes,I need to know if there should be a compatibility of the new pools or if this is normal behavior?
Especially if I upgrade my pools, there'll probably be no turning back...
On the good side, my old pools don't seem affected at all and mount correctly on both versions.