Last time I had a similar issue, we fixed it by issuing a forcelip via luxadm. Some might look at it as if it was a demon but it helped me in the past.
To list the ports:
Then reinitialize the one giving you headache via -e forcelip
But be careful:
Might be worth opening a case with Oracle. Let us know what they recommend or if you give my idea a shot.
hi fren
i am facing this problem
i have sun 6140 storage
30 volumes
bt my vxdisk list output is showing 37 disk
which shd nt b there
has neone faced this proble earlier
vxdiks list output is like this
SUN6140-2_0 auto - - online c4t201700A0B84853C0d2s2
SUN6140-2_1 auto - - online... (13 Replies)
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Hi,
I have a sun 440, it already has LUN's configured with MPXIO.
I just had more LUNS added, I did devfsadm and cfgadm -al, and they're showing up twice in "Format". :confused:
There are no new fiber cables or HBA's involved, same physical setup, just adding LUNS.
Aren't they... (0 Replies)
When I try to configure my HBA ports on Solaris 10; I cant see any output.
bash-3.2# mpathadm list lu
bash-3.2#
I checked /kernel/drv/fp.conf file.
...
mpxio-disable="no";
...
What shall I check more? what shall I do?
---------- Post updated at 10:18 AM ---------- Previous update was... (0 Replies)
How can i remove LUN's from solaris 10 those are unmapped from SAN?
from storage side i got confirmation that they removed lun. but in my solaris box still it's visible.
i tried below.
root@globalares2.example.com #luxadm -e offline /dev/rdsk/c2t600D02310007D16C42FF09E24B5B8255d0s2... (7 Replies)
Hi
I have a server running solaris 10 in which the NetAppadmin has just presented one LUN of 200Gb, but when running:
bash-3.2# format
Searching for disks...done
c3t500A09828DE3E799d1: configured with capacity of 199.94GB
c3t500A09829DE3E799d1: configured with capacity of 199.94GB
... (5 Replies)
Hi all, I have the following LUN which is showing OK with its two paths:
DEVICE PROPERTIES for disk: /dev/rdsk/c23t500507630A3BC579d123s2
Vendor: IBM
Product ID: 2107900
Revision: 3010
Serial Num: 75WB0114900
Unformatted capacity:... (13 Replies)
Hello,
Looking for some guidance to changing how an AIX 6.1 server sees its luns. Presently they're connected via 1GB iscsi but I want to change it to 4GB fiber channel. Anyone done this before and if so is it an easy step?
I'm thinking this can be done in this order:
unmount the... (5 Replies)
We are using Solaris 11 Logical Domains. We NFS share a disk backup area from one LDom to other servers. The share is on a single 1.5 Tb LUN presented to the Control Domain, and as a virtual disk on the NFS server LDom. A 1.5 Tb zpool has been created on the LDom. We now need to provide more disk... (2 Replies)
Discussion started by: SallyB
2 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS --predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO bup-midx(1), bup-save(1)BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown-bup-margin(1)