OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads up: 'zpool history' on-disk version change

Date: Tue, 20 Mar 2007 14:40:34 -0700
From: eric kustarz <eric.kustarz at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: Heads up: 'zpool history' on-disk version change

If you don't use ZFS or don't have any ZFS pools with history  
recorded (you can find out via 'zpool history'), then you can safely  
ignore the rest of this message.

I just integrated:
6529406 zpool history needs to bump the on-disk version

The original CR for 'zpool history':
6343741 want to store a command history on disk
was integrated into snv_51.

But wait, 'zpool history' has existed for several months, aren't we  
revising, um, history here?

It was originally believed that even though 'zpool history' added  
additional on-disk information it didn't need to bump the on-disk  
version.  My testing verified this to be true.  Turns out my testing  
was incomplete.  There is an edge case where if you have a pool with  
history recorded then you cannot move that pool to a pre-snv_51  
machine if that machine is also a different endianness.  If you do,  
then the load/import of the pool will cause a panic.  Please note:  
there is no corruption here.  If the machine is the same endianness,  
then the load/import will work just fine.

In order to again access your history, you will need to do a 'zpool  
upgrade', such as:

fsh-hake# zpool history wombat
History for 'wombat':
cannot get history for pool 'wombat', pool must be upgraded:  
unsupported version
fsh-hake# zpool upgrade wombat
This system is currently running ZFS version 4.
Successfully upgraded 'wombat' from version 3 to version 4
fsh-hake# zpool history wombat
History for 'wombat':
2007-03-19.19:01:55 zpool upgrade wombat

fsh-hake#

If your pool already has history, that data will be preserved and  
retrievable once again after you do the 'zpool upgrade'.

A reminder about 'zpool upgrade': once you upgrade, the pool can no  
longer be accessed by systems running older versions of ZFS.  Please  
see the zpool(1M) manpage.

If you have any further questions, feel free to send them my way.

controlling the present,
eric