Re: managing rhel disk space
On Tue, September 14, 2010 07:10, Donald Russell wrote: > I have a RHEL 5.5 system running on zVM 5.4... > > I've recently received a request to add two more file systems of 1 GB and > 2GB and mount them at /var/something-something and > /opt/something-something > > There is already enough free space in those directories to accommodate > their > request, so I just created the directories for them. > > However, they're insisting they be separate file systems so they can't > accidentally exceed the expected max usage. The best answers are "LVM" and/or quotas. LVMs are probably more reliable than quotas, to be honest. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: managing rhel disk space
You can do a vgdisplay -v rootvg ...should show you the minidisks (/dev/dasdb1, etc). lsdasd to sort out which minidisk number goes with which dasd number. You may be able shrink the size of the existing /var and then give it to another logical volume... but I'm not as familiar with doing this. You could just create another logical volume (custvar) and mount that under /var where they want it I guess.. I take it they want to manage their own space under /var and not the whole system's? Scott Rohling On Mon, Sep 13, 2010 at 1:56 PM, Donald Russell wrote: > /var has it's own filesystem using lvm, but now they want another directory > under /var to have it's own as well. The existing /var has enough space for > the new request. > > From what I'm hearing (reading) it seems I'll have to allocate/assign new > minidisks (ECKD) or LUNs (SCSI) and create new filesystems. The only > purpose > is to prevent accidental overflow. Each of those file systems will be > logical volums so they can be expanded later by adding more minidisks and > adding the space to the correct logical volume group hmm, I can see > this > turning into a nightware of keeping track of what's on what. > > i.e. Given a list of file systems (from the df command), how can I > determine > which minidisks or LUNs those are actually on. For example, /var is the > mount point for something called /dev/mapper/rootvg-varlv That could be > made > up of several minidisks etc... > > > > > On Mon, Sep 13, 2010 at 12:23, RPN01 wrote: > > > In your case it might require a time machine, but we've used LVM for this > > type of thing. You put the amount of space there you need, rather than > way > > over-allocating space. Then in situations like this, you add the needed > > space, and create the mount points they need. Also, down the road, when > > they > > discover that they really should have asked for double that amount, you > > just > > add the space to the volume group, give it to the logical volume, and > > extend > > the filesystem. It really works as advertised. > > > > -- > > Robert P. Nix Mayo Foundation.~. > > RO-OC-1-18 200 First Street SW/V\ > > 507-284-0844 Rochester, MN 55905 /( )\ > > -^^-^^ > > "In theory, theory and practice are the same, but > > in practice, theory and practice are different." > > > > > > > > On 9/13/10 2:10 PM, "Donald Russell" wrote: > > > > > I have a RHEL 5.5 system running on zVM 5.4... > > > > > > I've recently received a request to add two more file systems of 1 GB > and > > > 2GB and mount them at /var/something-something and > > /opt/something-something > > > > > > There is already enough free space in those directories to accommodate > > their > > > request, so I just created the directories for them. > > > > > > However, they're insisting they be separate file systems so they can't > > > accidentally exceed the expected max usage. > > > > > > So, my question is... do I have to attach new minidisks or LUNs(?) of > the > > > appropriate sizes or can quotas set a cap on the amount of space a > > directory > > > can use? I know I can set individual user quotas, but I've a feeling > > there's > > > more than one user of this space. > > > > > > What do other people do in these situations? Adding MDISKs or LUNs > sounds > > > extreme to me... > > > > > > I was looking at the mkfs command, but that seems to require > > > unused/allocated part of an existing partition all non-cms disk > space > > > that's attached to the VM id is allocated to Linux. Can I reduce the > size > > of > > > a logical volume, then create a new filesystem from that freed space? > > > > > > Thanks > > > > > > -- > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > > visit > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > -- > > > For more information on Linux on System z, visit > > > http://wiki.linuxvm.org/ > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For
Re: managing rhel disk space
/var has it's own filesystem using lvm, but now they want another directory under /var to have it's own as well. The existing /var has enough space for the new request. >From what I'm hearing (reading) it seems I'll have to allocate/assign new minidisks (ECKD) or LUNs (SCSI) and create new filesystems. The only purpose is to prevent accidental overflow. Each of those file systems will be logical volums so they can be expanded later by adding more minidisks and adding the space to the correct logical volume group hmm, I can see this turning into a nightware of keeping track of what's on what. i.e. Given a list of file systems (from the df command), how can I determine which minidisks or LUNs those are actually on. For example, /var is the mount point for something called /dev/mapper/rootvg-varlv That could be made up of several minidisks etc... On Mon, Sep 13, 2010 at 12:23, RPN01 wrote: > In your case it might require a time machine, but we've used LVM for this > type of thing. You put the amount of space there you need, rather than way > over-allocating space. Then in situations like this, you add the needed > space, and create the mount points they need. Also, down the road, when > they > discover that they really should have asked for double that amount, you > just > add the space to the volume group, give it to the logical volume, and > extend > the filesystem. It really works as advertised. > > -- > Robert P. Nix Mayo Foundation.~. > RO-OC-1-18 200 First Street SW/V\ > 507-284-0844 Rochester, MN 55905 /( )\ > -^^-^^ > "In theory, theory and practice are the same, but > in practice, theory and practice are different." > > > > On 9/13/10 2:10 PM, "Donald Russell" wrote: > > > I have a RHEL 5.5 system running on zVM 5.4... > > > > I've recently received a request to add two more file systems of 1 GB and > > 2GB and mount them at /var/something-something and > /opt/something-something > > > > There is already enough free space in those directories to accommodate > their > > request, so I just created the directories for them. > > > > However, they're insisting they be separate file systems so they can't > > accidentally exceed the expected max usage. > > > > So, my question is... do I have to attach new minidisks or LUNs(?) of the > > appropriate sizes or can quotas set a cap on the amount of space a > directory > > can use? I know I can set individual user quotas, but I've a feeling > there's > > more than one user of this space. > > > > What do other people do in these situations? Adding MDISKs or LUNs sounds > > extreme to me... > > > > I was looking at the mkfs command, but that seems to require > > unused/allocated part of an existing partition all non-cms disk space > > that's attached to the VM id is allocated to Linux. Can I reduce the size > of > > a logical volume, then create a new filesystem from that freed space? > > > > Thanks > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: managing rhel disk space
Yep -- your answer is LVM ... for the Linux OS directories - I typically recommend: - Keep root as a single partition on a minidisk (not LVM) on it's own filesystem. /boot should stay in this partition or have one of it's own. - Create a 'system' volume group with one or more minidisks (1 to end - don't mess around with smaller ones unless you're using 3390-27 or bigger) - Create logical volumes (I just name them the same as the mount point - var,tmp,usr, etc) for each mount point you want separated: /var, /tmp, /opt, /usr, /home and give them the space 'required'. mkfs a file system on each logical volume and indicate they should be mounted in /etc/fstab (e.g./dev/system/usr/usr ext3 defaults 1 1) When more space is needed - just add another minidisk to the system volume group - divide up the new space to the logical volumes that need it -- resize the filesystems - done. For application data, database, etc -- make a different volume group (e.g. appdata) and 1 or more logical volumes within that -- then you can expand them the same same way. Scott Rohling On Mon, Sep 13, 2010 at 1:23 PM, RPN01 wrote: > In your case it might require a time machine, but we've used LVM for this > type of thing. You put the amount of space there you need, rather than way > over-allocating space. Then in situations like this, you add the needed > space, and create the mount points they need. Also, down the road, when > they > discover that they really should have asked for double that amount, you > just > add the space to the volume group, give it to the logical volume, and > extend > the filesystem. It really works as advertised. > > -- > Robert P. Nix Mayo Foundation.~. > RO-OC-1-18 200 First Street SW/V\ > 507-284-0844 Rochester, MN 55905 /( )\ > -^^-^^ > "In theory, theory and practice are the same, but > in practice, theory and practice are different." > > > > On 9/13/10 2:10 PM, "Donald Russell" wrote: > > > I have a RHEL 5.5 system running on zVM 5.4... > > > > I've recently received a request to add two more file systems of 1 GB and > > 2GB and mount them at /var/something-something and > /opt/something-something > > > > There is already enough free space in those directories to accommodate > their > > request, so I just created the directories for them. > > > > However, they're insisting they be separate file systems so they can't > > accidentally exceed the expected max usage. > > > > So, my question is... do I have to attach new minidisks or LUNs(?) of the > > appropriate sizes or can quotas set a cap on the amount of space a > directory > > can use? I know I can set individual user quotas, but I've a feeling > there's > > more than one user of this space. > > > > What do other people do in these situations? Adding MDISKs or LUNs sounds > > extreme to me... > > > > I was looking at the mkfs command, but that seems to require > > unused/allocated part of an existing partition all non-cms disk space > > that's attached to the VM id is allocated to Linux. Can I reduce the size > of > > a logical volume, then create a new filesystem from that freed space? > > > > Thanks > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: managing rhel disk space
In your case it might require a time machine, but we've used LVM for this type of thing. You put the amount of space there you need, rather than way over-allocating space. Then in situations like this, you add the needed space, and create the mount points they need. Also, down the road, when they discover that they really should have asked for double that amount, you just add the space to the volume group, give it to the logical volume, and extend the filesystem. It really works as advertised. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 9/13/10 2:10 PM, "Donald Russell" wrote: > I have a RHEL 5.5 system running on zVM 5.4... > > I've recently received a request to add two more file systems of 1 GB and > 2GB and mount them at /var/something-something and /opt/something-something > > There is already enough free space in those directories to accommodate their > request, so I just created the directories for them. > > However, they're insisting they be separate file systems so they can't > accidentally exceed the expected max usage. > > So, my question is... do I have to attach new minidisks or LUNs(?) of the > appropriate sizes or can quotas set a cap on the amount of space a directory > can use? I know I can set individual user quotas, but I've a feeling there's > more than one user of this space. > > What do other people do in these situations? Adding MDISKs or LUNs sounds > extreme to me... > > I was looking at the mkfs command, but that seems to require > unused/allocated part of an existing partition all non-cms disk space > that's attached to the VM id is allocated to Linux. Can I reduce the size of > a logical volume, then create a new filesystem from that freed space? > > Thanks > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: managing rhel disk space
You can easily add new minidisks. You'll need to change zipl.conf to address the new minidisks. You'll also need to recreate your initrd. Lastly don't forget to run 'zipl -V' Once you're back up you can make the PVs and add them to your VG and then create your new filesystems. russell@gmail.com Sent by: LINUX-390@VM.MARIST.EDU 09/13/2010 03:12 PM Please respond to LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject managing rhel disk space I have a RHEL 5.5 system running on zVM 5.4... I've recently received a request to add two more file systems of 1 GB and 2GB and mount them at /var/something-something and /opt/something-something There is already enough free space in those directories to accommodate their request, so I just created the directories for them. However, they're insisting they be separate file systems so they can't accidentally exceed the expected max usage. So, my question is... do I have to attach new minidisks or LUNs(?) of the appropriate sizes or can quotas set a cap on the amount of space a directory can use? I know I can set individual user quotas, but I've a feeling there's more than one user of this space. What do other people do in these situations? Adding MDISKs or LUNs sounds extreme to me... I was looking at the mkfs command, but that seems to require unused/allocated part of an existing partition all non-cms disk space that's attached to the VM id is allocated to Linux. Can I reduce the size of a logical volume, then create a new filesystem from that freed space? Thanks -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
managing rhel disk space
I have a RHEL 5.5 system running on zVM 5.4... I've recently received a request to add two more file systems of 1 GB and 2GB and mount them at /var/something-something and /opt/something-something There is already enough free space in those directories to accommodate their request, so I just created the directories for them. However, they're insisting they be separate file systems so they can't accidentally exceed the expected max usage. So, my question is... do I have to attach new minidisks or LUNs(?) of the appropriate sizes or can quotas set a cap on the amount of space a directory can use? I know I can set individual user quotas, but I've a feeling there's more than one user of this space. What do other people do in these situations? Adding MDISKs or LUNs sounds extreme to me... I was looking at the mkfs command, but that seems to require unused/allocated part of an existing partition all non-cms disk space that's attached to the VM id is allocated to Linux. Can I reduce the size of a logical volume, then create a new filesystem from that freed space? Thanks -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Debian install...
Anyone done a Debian install on z/VM? I’m attempting to install Lenny, and I get to the DASD partitioning. I set up my disks the way I want them, tell it to begin writing, and get the following: ┌──┤ [!!] Partition disks ├── │ ERROR!!! │ │ VTOC: seeking on device failed -- vtoc_write_label │ │ Could not write VTOC labels. │ ││ │ │ ││ └─ The install won’t go any further from there. I know the disks are writable within the virtual machine; I was able to use cpfmtxa on them, and Debian was able to format them. I’ve tried just about every combination of formatting and not formatting, partitioning and not partitioning that I can think of. We have 50 RedHat and SuSE images running, so it’s not that we don’t know what we’re doing in general. There must be a way to make this work, or they wouldn’t have released it. Does anyone have a clue as to how to do it correctly? -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
