10 More Discussions You Might Find Interesting
1. Solaris
Hi everybody,
few days ago we had a big issue with one of our solaris10 server.
Suddenly while my colleague was working on it for some troubleshooting he realized that the performance started to degrade.
At the end it reached the point that was not even possible to login usng the local console... (7 Replies)
Discussion started by: bdegiovanni
7 Replies
2. AIX
Hello,
AIX 6.1 TL7 SP6
POwerHA 6.1 SP10
I was experimenting with new hacmp build. It's 3-node cluster build on AIX 6.1 lpars. It contains Ethernet and diskhb networks. Shared vg disk is SAN disk. Two nodes see disk using vscsi, third node sees disk using npiv. Application is db2 server.
... (4 Replies)
Discussion started by: vilius
4 Replies
3. Solaris
I have a Sun-Fire-V210, the Server hangs for sometime and evn console wont be abled to access and after sometime the server comes back active. the messages file shows this , whats causing this ?
# tail -500 messages
Jan 25 07:02:16 xxxxxxxxxxxxx Corrupt label; wrong magic number
Jan 25... (2 Replies)
Discussion started by: Sojourner
2 Replies
4. Solaris
Hello all,
The issue is
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap 4.0G 4.0G 8.7M 100% /tmp
# du -sh /tmp/
87M /tmp
By now you probably will say that this is open file destriptor issue.
Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies
5. AIX
Dear All,
We are on AIX OS, /tmp directory is filled up to 99% percent,
Please suggest, How to get free space for "/tmp"?
which files can be deleted from /tmp? and How to delete it? is there any commands.....
Thanks in advance,
Its very urgent, Helpful answers will be appreciated,
Please... (7 Replies)
Discussion started by: kak
7 Replies
6. AIX
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. AIX
The /tmp is 100% full, I found there are the following big files/directory:
1301500 syslog.out.58
166692 vac
158552 install.dir.2928686
158552 install.dir.2236636
110980 install.dir.2887698
/tmp/vac have some files like :
.toc ... (3 Replies)
Discussion started by: rainbow_bean
3 Replies
8. Solaris
Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again.
The server has not rebooted but here are the first errors in the messages log... (5 Replies)
Discussion started by: frustrated1
5 Replies
9. AIX
good morning
The /tmp filesystem is full at 99 %
I have do a "rm" but the size is the same.
so i think that a process is always alive, but how can i do to know it ? (because I have deleted some file in /tmp)
thank you (9 Replies)
Discussion started by: pascalbout
9 Replies
10. UNIX for Dummies Questions & Answers
I am running AIX 3 4.
When I do a df I get:
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 32768 10232 69% 1309 16% /
/dev/hd2 917504 86360 91% 19744 18% /usr
/dev/hd9var 131072 67712 49% 617 ... (11 Replies)
Discussion started by: szodiac
11 Replies
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)
