07-23-2012
Thank you. I got that.. But i want to know what is best practice or recommended value??
10 More Discussions You Might Find Interesting
1. AIX
(0 Replies)
Discussion started by: mhenryj
0 Replies
2. AIX
Hello
I am a noobie to HACMP
I have 2 55A servers and a 7031 disk subsystem
For HACMP to work, do I need to have the hdisks on both servers to match the same drives??
The hdisks on each box are currently different:
hdisk0 and hdisk1 are the internal disks and hdisk2-5 are on the D24 on... (1 Reply)
Discussion started by: mhenryj
1 Replies
3. HP-UX
Hi,
Can anybody advice whether it is possible to configure HACMP in HP-UX Server.
To my knowledge HACMP is IBM Solution.
Thanks && Regards,
N. Poorna Chandra Rao. (2 Replies)
Discussion started by: npcrao
2 Replies
4. AIX
Hi,
I needed space on a FS, and when I've added the space on the filesystem, I did it trough the regular smitty fs inteface and not with smitty cl_lvm.
Can someone help me to repair the situat before a faileover happen ?
Thanks for your help,:mad: (13 Replies)
Discussion started by: azzed27
13 Replies
5. AIX
Hi,
Can we use network for heartbeat, I mean can we use different network card for heartbeat. (6 Replies)
Discussion started by: vjm
6 Replies
6. AIX
hi
can anyone explain the concepts of HACMP and configuration (step by step) (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
7. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
8. AIX
Hi.
We have a two node HA cluster.
We got a request to change one of the VG name?
Is there an option to do this online ? If it requires downtime can someone please explain me the steps for doing it ?
Let me know if you need any outputs from the servers (1 Reply)
Discussion started by: newtoaixos
1 Replies
9. AIX
Hi,
I have question about HA. I have 2 node cluster (node A and node B). I have configured network and disk HB. If my network is up and i remove both the fc cables from node A will my cluster failover to node B? I have checked and its not working, if i want my cluster to failover in this... (5 Replies)
Discussion started by: powerAIX
5 Replies
10. AIX
hello
ive 2 nodes aix 6100-04-10-1119 with hacmp 6.1.0.0
my qustion is :
can i add default gateway to one member node with hacmp a live or to do take over to realse one of the members ?
thanks
When it is urgent, then open the thread up in the appropriate subforum next time, thanks. (3 Replies)
Discussion started by: ariec
3 Replies
LEARN ABOUT XFREE86
git-pack-refs
GIT-PACK-REFS(1) Git Manual GIT-PACK-REFS(1)
NAME
git-pack-refs - Pack heads and tags for efficient repository access
SYNOPSIS
git pack-refs [--all] [--no-prune]
DESCRIPTION
Traditionally, tips of branches and tags (collectively known as refs) were stored one file per ref in a (sub)directory under $GIT_DIR/refs
directory. While many branch tips tend to be updated often, most tags and some branch tips are never updated. When a repository has
hundreds or thousands of tags, this one-file-per-ref format both wastes storage and hurts performance.
This command is used to solve the storage and performance problem by storing the refs in a single file, $GIT_DIR/packed-refs. When a ref is
missing from the traditional $GIT_DIR/refs directory hierarchy, it is looked up in this file and used if found.
Subsequent updates to branches always create new files under $GIT_DIR/refs directory hierarchy.
A recommended practice to deal with a repository with too many refs is to pack its refs with --all once, and occasionally run git
pack-refs. Tags are by definition stationary and are not expected to change. Branch heads will be packed with the initial pack-refs --all,
but only the currently active branch heads will become unpacked, and the next pack-refs (without --all) will leave them unpacked.
OPTIONS
--all
The command by default packs all tags and refs that are already packed, and leaves other refs alone. This is because branches are
expected to be actively developed and packing their tips does not help performance. This option causes branch tips to be packed as
well. Useful for a repository with many branches of historical interests.
--no-prune
The command usually removes loose refs under $GIT_DIR/refs hierarchy after packing them. This option tells it not to.
BUGS
Older documentation written before the packed-refs mechanism was introduced may still say things like ".git/refs/heads/<branch> file
exists" when it means "branch <branch> exists".
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-PACK-REFS(1)