11-12-2013
You can easily upgrade the zpool version to whatever the most current revision is that's supported on your platform. As the documentation says, you can upgrade but it's not backwards compatible.
Here's the Oracle link:
http://docs.oracle.com/cd/E19253-01/...ikw/index.html
7 More Discussions You Might Find Interesting
1. Solaris
Hi All,
I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties.
File seems to be in packed format.I am not sure how to unpack it.
But from opensolaris code base we can see that they have used libz for uncompromising this file, but... (0 Replies)
Discussion started by: shailesh_111
0 Replies
2. Solaris
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
Discussion started by: incredible
10 Replies
3. BSD
I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error:
# zpool create zfspool /dev/da0s1a
cannot create 'zfspool': no such pool or dataset
# zpool create zfspool /dev/da0
cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies
4. Solaris
running VM server for Sparc on a Solaris 11 server. I have a Guest LDOm that had two seperate zpools running, one for the zones and one for the OS. The OS was corrupted and had to be replaced. The zones zfs file system is intact I think. I still have access to the disk and can still see it in... (3 Replies)
Discussion started by: os2mac
3 Replies
5. Solaris
HI,
Is there any GUI or web ui to administrate zfs/zpool.
i want to monitor/expand/migrate zfs from one machine to another machine (0 Replies)
Discussion started by: bentech4u
0 Replies
6. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies
7. Solaris
Hello,
I am upgrading Veritas from 5.1 to 6.0.1/6.0.5 in a Solaris 10 u8 server with OS mirrored (rpool) in zfs/zpool configuration.
I need to split it to have a quick way to backout in case of failure (make splitted mirror side bootable for a quick revert, like booting from it). I remember... (3 Replies)
Discussion started by: feroccimx
3 Replies
LEARN ABOUT DEBIAN
ditrack
DITRACK(1) General Commands Manual DITRACK(1)
NAME
dt - DITrack command line client tool
SYNOPSIS
dt command [options] [args]
dt-createdb repository-url issue-db-dir local-wc
dt-upgrade-0.7-db issue-db-dir
OVERVIEW
DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead
of a backend database. It is written in Python and runs in UNIX environment (*BSD, Linux, MacOS X).
The project is inspired by the idea of Subissue issue tracking system.
However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major rethought
of the issue tracking system paradigm. The main difference is that instead of sticking to the centralized model (one database, one web
interface, one mail integration machinery), DITrack treats underlying Subversion storage as a versioned distributed file system which
enables benefits of truly distributed operation mode.
For more information about the DITrack project, visit http://www.ditrack.org.
Documentation for DITrack and its tools, including detailed usage explanations of the dt and dt-createdb programs, can be found at
/usr/share/doc/ditrack/html/index.html.
Run `dt help' to access the built-in tool documentation.
Automatic upgrade is possible for databases created by DITrack 0.7. If you are upgrading from previous version of DITrack, use the upgrage
utility from DITrack 0.7 first.
To upgrade a database run the dt-upgrade-0.7-db script, passing the database path as the argument, like:
dt-upgrade-0.7-db /home/user/ditrack-database
The upgrade procedure merely modifies the working copy (nothing gets committed to the repository). So, when done, you should commit the
changes manually.
April 2007 DITRACK(1)