09-08-2011
Yeah, there isn't much point in setting up your meta database on your ZFS disks. You should have your meta database on the disks that you're actually using for LVM.
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
If solaris has metadb services on the disk, it means that it has a HW raid controller. Or what.
Thanks in advance. (1 Reply)
Discussion started by: itik
1 Replies
2. Solaris
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest (4 Replies)
Discussion started by: kumarmani
4 Replies
3. Solaris
Hello,
I have a 520GB SAN resource connected to the server via FC (4Gbit).
In the next step he wants to create pool storage:
After 15 hours Pool has not yet created...
Is such a long waiting time is normal? Should I have done?
Regards (1 Reply)
Discussion started by: bieszczaders
1 Replies
4. Solaris
I have a solaris zone of 12 GB and i have to increase the / filesystem to 31GB as requested. Earlier I had expanded filesystems other than / by setting quota to new value like "zfs set quota=new value mountpoint" but I am not sure whether its a good practice in zfs because by default in my... (5 Replies)
Discussion started by: vikkash
5 Replies
5. 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
6. Solaris
Check Solaris VM Databases metadb does not have enough information about logical volumes. Current value is 0%
I have checked the SVM status, all disks are good state and synched perfectly. no errors in metadb -i.
what is this alert exact mean? what we have to check for the value?
Please... (1 Reply)
Discussion started by: Naveen.6025
1 Replies
7. Solaris
Hi everyone,
I'm hoping someone can help me out here. I've googled lots and don't think I can find an easy answer to this.
We're in the process of upgrading Solaris from v10 5/08 to v10 9/10. The zpools for luns are currently at version 10, and I understand Solaris v10 9/10 has support for... (3 Replies)
Discussion started by: badoshi
3 Replies
8. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
9. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
10. Solaris
how to recovery metadb?
Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
LEARN ABOUT LINUX
inviso_rt_meta
inviso_rt_meta(3erl) Erlang Module Definition inviso_rt_meta(3erl)
NAME
inviso_rt_meta - Direct API to the Inviso Runtime Component's meta tracer
DESCRIPTION
This module provides a direct API to the inviso meta tracer. These functions are only meant to be used in meta tracing CallFunc and Remove-
Func .
It can sometimes be necessary to manipulate meta match-patterns from CallFunc s and RemoveFunc s. The problem then is that call-funcs and
remove-funcs are meta trace call-backs executed inside the inviso meta tracer's context. Hence making calls to the regular API's manipulat-
ing meta trace-patterns will hang the inviso meta tracer!.
To remedy this problem, a number of useful tpm-functions are available in this API. It must be understood that their actions are local to
the Erlang node where they are called.
EXPORTS
tpm_ms(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}
See inviso:tpm_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is
called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
tpm_ms_tracer(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}
See inviso:tpm_ms_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function
is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
list_tpm_ms(Mod,Func,Arity) -> [MSname]
Returns a list of all MSname in use for Mod:Func/Arity . This can be useful instead of having to have an own-implemented database
over currently in use meta match-functions for a particular function.
ctpm_ms(Mod,Func,Arity,MSname) -> ok
See inviso:ctpm_ms/5 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is
called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
get_tracer() -> Tracer
Types Tracer = pid() | port()
Returns the pid or port acting as the receiver of regular trace messages. This is useful if it is necessary to manipulate meta
trace-patterns by hand (using erlang:trace_pattern/3 ) and the {tracer,Tracer} must be used in one of the match-function bodies.
Ericsson AB inviso 0.6.2 inviso_rt_meta(3erl)