02-01-2015
Your setup still does not offer redundancy. If c3t5000CCA012B3E751d0 or c3t5000CCA012B39541d0 fails, the whole pool will become unavailable.
10 More Discussions You Might Find Interesting
1. Solaris
I had a pool which was exported and due to some issues on my SAN i was never able to import it again. Can anyone tell me how can i destroy the exported pool to free up the LUN. I tried to create a new pool on the same pool but it gives me following error
# zpool create emcpool4 emcpower0c... (0 Replies)
Discussion started by: fugitive
0 Replies
2. Solaris
I am not seeing anyway to remove a LUN from a Zpool...
Am I missing something? or do i have to destroy the zpool and recreate it? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
3. Red Hat
Hi Everyone,
I have added new Virtual disk to OS. The main point is I need to bring this whole Disk into LVM control, is it necessary to partition the disk using fdisk command and assign partition type as '8e', or can I directly add that disk into LVM, by running pvcreate command with out... (2 Replies)
Discussion started by: bobby320
2 Replies
4. AIX
Hi
I have one of the disk missing in my NIMVG. My doubt is can I remove this hdisk2 online ? few of the file systems seems to be spread over 7 PV's. that's why i'm worried. Can someone suggest if I can replace this disk online. Also how to check if there is some data present in hdisk2 alone... (2 Replies)
Discussion started by: newtoaixos
2 Replies
5. Solaris
Hi ,
One of my zone went down and when i booted it up i could see the pool in degraded state with some check sum errors . we have brought the pool online after scrubbing. But few files are showing this error
Bad exchange descriptor
Please let me know how to remove these files (2 Replies)
Discussion started by: chidori
2 Replies
6. Solaris
Hi,
Quick question.
I have a data zpool that consists of 1 disk.
pool: data
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
c0t50002AC0014B06BEd0 ONLINE... (2 Replies)
Discussion started by: general_lee
2 Replies
7. AIX
Dear All,
I created a new partition through "Integrated Virtualization Manager" but there have an error when I added a new disk to the partition. The disk already created without any issue,
Below error is to add the disk to the partition
An error occured while modifying the assignments... (5 Replies)
Discussion started by: lckdanny
5 Replies
8. Solaris
Hello,
I need some help in recovering ZFS pool. Here is scenerio. There are two disks -
c0t0d0 - This is good disk. I cloned it from other server and boot server from this disk.
c0t1d0 - This is original disk of this server, having errors. I am able to mount it on /mnt. So that I can copy... (1 Reply)
Discussion started by: solaris_1977
1 Replies
9. Solaris
issue,
I had a zpool which was full
pool_temp1 199G 197G 1.56G 99% ONLINE -
pool_temp2 199G 196G 3.09G 98% ONLINE -
as you can see, full
so I replaced with a larger disk.
zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies
10. Solaris
On an OmniOS server, I removed a single-disk pool I was using for testing.
Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore.
# zpool import
pool: fido
id: 7452075738474086658
state: FAULTED
status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
LEARN ABOUT NETBSD
memoryallocators
MEMORYALLOCATORS(9) BSD Kernel Developer's Manual MEMORYALLOCATORS(9)
NAME
memoryallocators -- introduction to kernel memory allocators
DESCRIPTION
The NetBSD kernel provides several memory allocators, each with different characteristics and purpose. This document summarizes the main
differences between them.
The Kmem Allocator
The kmem allocator is modelled after an interface of similar name implemented in Solaris. This is main general purpose allocator in the ker-
nel.
It is implemented on-top of the vmem(9) resource allocator (beyond the scope of this document), meaning it will be using pool_cache(9) inter-
nally to speed-up common (small) sized allocations.
It requires no setup, but cannot be used from interrupt context.
See kmem(9) for more details.
The Pool Allocator
The pool(9) allocator is a fixed-size memory allocator. It requires setup (to initialize a memory pool) and is interrupt-safe.
See pool(9) for more details.
The Pool Cache Allocator
The pool cache allocator works on-top of the pool(9) allocator, also allowing fixed-size allocation only, requires setup, and is interrupt-
safe.
The pool cache allocator is expected to be faster than other allocators, including the ``normal'' pool allocator.
In the future this allocator is expected to have a per-CPU cache.
See pool_cache(9) for more details.
The UVM Kernel Memory Allocator
This is a low-level memory allocator interface. It allows variable-sized allocations in multiples of PAGE_SIZE, and can be used to allocate
both wired and pageable kernel memory.
See uvm(9) for more details.
SEE ALSO
intro(9), kmem(9), pool(9), pool_cache(9), uvm(9), vmem(9)
AUTHORS
Elad Efrat <elad@NetBSD.org>
YAMAMOTO Takashi <yamt@NetBSD.org>
BSD
August 3, 2009 BSD