04-10-2019
Hi Bakunin,
Quote:
Yes, big VGs have still a limitation of how many PPs can reside on a single PV AND they have a restriction of how many PVs can be in a VG, although these limits are higher than in a classic VG. The scalable VG only has one upper limit and that is the number of PPs overall, in the whole VG. There is no limit of how many PPs can be in a single PV any more. You can set the maximum number of PPs for the whole VG at the creation of the VG and my suggestion is to set it to the maximum possible of ~2 million PPs as i told you already.
So we can convert it to scalable VG and then we can add the 1 TB disk later?
Regarding the PP size yes it's ridiculous, it was created by the ex-admin and now I inherited all the legacy
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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)
Discussion started by: steve99
2 Replies
2. HP-UX
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)
Discussion started by: pedro_lezaeta
6 Replies
3. AIX
Hi Everybody,
Is it possible to extend a Filesystem by adding a new LV that exist on different VG to this Filesystem?
Thanks in advance. (6 Replies)
Discussion started by: aldowsary
6 Replies
4. Solaris
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)
Discussion started by: jackiebaron
5 Replies
5. Filesystems, Disks and Memory
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)
Discussion started by: jackiebaron
1 Replies
6. Solaris
Hi all,
currently , my root filesystem already reach 90 ++%
I already add more cylinder in the root partition as below
Part Tag Flag Cylinders Size Blocks
0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300
1 swap wu 1 - ... (11 Replies)
Discussion started by: SmartAntz
11 Replies
7. Red Hat
Hi,
I have recently increased the size of my pv and I am now attempting to increase the lv but I get the following error:
# vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata... (7 Replies)
Discussion started by: Duffs22
7 Replies
8. AIX
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)
Discussion started by: unclefab
3 Replies
9. Linux
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)
Discussion started by: Gabriander
0 Replies
10. Red Hat
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 SUSE
limits.conf
LIMITS.CONF(5) Linux-PAM Manual LIMITS.CONF(5)
NAME
limits.conf - configuration file for the pam_limits module
DESCRIPTION
The syntax of the lines is as follows:
<domain> <type> <item> <value>
The fields listed above should be filled as follows:
<domain>
o a username
o a groupname, with @group syntax. This should not be confused with netgroups.
o the wildcard *, for default entry.
o the wildcard %, for maxlogins limit only, can also be used with %group syntax.
<type>
hard
for enforcing hard resource limits. These limits are set by the superuser and enforced by the Kernel. The user cannot raise his
requirement of system resources above such values.
soft
for enforcing soft resource limits. These limits are ones that the user can move up or down within the permitted range by any
pre-existing hard limits. The values specified with this token can be thought of as default values, for normal system usage.
-
for enforcing both soft and hard resource limits together.
Note, if you specify a type of '-' but neglect to supply the item and value fields then the module will never enforce any limits on
the specified user/group etc. .
<item>
core
limits the core file size (KB)
data
maximum data size (KB)
fsize
maximum filesize (KB)
memlock
maximum locked-in-memory address space (KB)
nofile
maximum number of open files
rss
maximum resident set size (KB) (Ignored in Linux 2.4.30 and higher)
stack
maximum stack size (KB)
cpu
maximum CPU time (minutes)
nproc
maximum number of processes
as
address space limit (KB)
maxlogins
maximum number of logins for this user except for this with uid=0
maxsyslogins
maximum number of logins on system
priority
the priority to run user process with (negative values boost process priority)
locks
maximum locked files (Linux 2.4 and higher)
sigpending
maximum number of pending signals (Linux 2.6 and higher)
msqqueue
maximum memory used by POSIX message queues (bytes) (Linux 2.6 and higher)
nice
maximum nice priority allowed to raise to (Linux 2.6.12 and higher) values: [-20,19]
rtprio
maximum realtime priority allowed for non-privileged processes (Linux 2.6.12 and higher)
All items support the values -1, unlimited or infinity indicating no limit, except for priority and nice.
If a hard limit or soft limit of a resource is set to a valid value, but outside of the supported range of the local system, the system may
reject the new limit or unexpected behavior may occur. If the control value required is used, the module will reject the login if a limit
could not be set.
In general, individual limits have priority over group limits, so if you impose no limits for admin group, but one of the members in this
group have a limits line, the user will have its limits set according to this line.
Also, please note that all limit settings are set per login. They are not global, nor are they permanent; existing only for the duration of
the session.
In the limits configuration file, the '#' character introduces a comment - after which the rest of the line is ignored.
The pam_limits module does report configuration problems found in its configuration file and errors via syslog(3).
EXAMPLES
These are some example lines which might be specified in /etc/security/limits.conf.
* soft core 0
* hard rss 10000
@student hard nproc 20
@faculty soft nproc 20
@faculty hard nproc 50
ftp hard nproc 0
@student - maxlogins 4
SEE ALSO
pam_limits(8), pam.d(5), pam(8), getrlimit(2) getrlimit(3p)
AUTHOR
pam_limits was initially written by Cristian Gafton <gafton@redhat.com>
Linux-PAM Manual 04/01/2010 LIMITS.CONF(5)