Hi!
How to extend /usr partition in rootvg on AIX 4.3.3-09?
I guess first I'll have to decrease the size of other partition(s) in rootvg?
Thank you! (2 Replies)
on the disk array (EMC Clariion cx300):
we added 3 disk and extended the LUN corresponding to HP-9000 (rp7410)
on HP-UX 11.11:
diskinfo /dev/rdsk/c10t0d0, show more disk space, but
vgdisplay vg13 does not show more space
So the problem is the disk had increased, but vgdisplay does not... (6 Replies)
I am running solaris 10 with Veritas. I want to extend a filesystem. It's an oracle partition (/ora12). How can I find out if there is space available to expand the filesystem and then how does one extend it.
I'm from the HPUX world and so LVM was always how I did things.
Thanks
jackie (5 Replies)
OK I'm sure this question has been posed far too many times.
I have solaris 10 x86 with NO Veritas or Disksuite filesystems. Below is the output of df -k
# df -k
Filesystem kbytes used avail capacity Mounted on
/ 10485760 547513 9317128 6% /
/dev... (1 Reply)
Hello,
i have a file :
2010-10-28 17:57:42.581
#$!pre-dump!$#00027cv
060400552|060730|0963.000.2|30000261282|137943|176141|theipia_|01232006|1|
060400553|060730|0963.000.2|30000261283|137943|176141|theipia_|01232006|1|... (3 Replies)
Hi all,
I need to extend a lv, but unfortunately I do not have enough space on my mirrored Volume group.
I've planned to add 2 more disks to this vg (for mirroring)
But ... what's the next steps to extend my lv using these 2 disks with a valid mirroring ?
1. extendvg myvg disk1 disk2... (3 Replies)
Hi friends iam new to unix. how to extend memory in UNIx.
what are the possible scenarios to increase memory.
I just noticed we have swap memory also but when and how to use it. and what is the correct way to increase RAM. please provide information or some useful commands. Thanks (2 Replies)
Hi all.
I have a Logical volume that I can't extend, with this error message:
server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv
Finding volume group aplic_vg
Archiving volume group "aplic_vg" metadata (seqno 75).
Extending logical volume siteminderwa_lv to... (0 Replies)
Hello,
I have redhat and centos systems that I've only been able to grow the VG by adding more disks. I've been searching the web for a way to extend a volume group by growing the physical disk only and not having to add a second disk. Is it possible?
I can do this with AIX, by just... (0 Replies)
Discussion started by: bbbngowc
0 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)