I have problems with this kind of thing on z/OS Unix. Our /tmp filesystem on z/OS is nearly a full volume with usage around 2% because DB2 was configured to write a log file to /tmp, and someone ran a load test that cause DB2 to write 1.2G of log data.
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Scott Rohling Sent: Friday, August 15, 2008 9:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem That was my first thought too... BUT - I can see how it could be useful to have free space in a VG and then assign it where it might be needed as it's needed within the VG. (Leave 1GB of the VG unassigned, and let the script assign it on an 'emergency' basis to the LV that is running low). More interesting is the notion of getting VM to assign the disk and then have it automatically added to the VG. (Think application data). If the method involves just have a bunch of VM minidisks already assigned to the guest, ready to be added - then I agree - why not just assign them now. Scott Rohling On Fri, Aug 15, 2008 at 10:20 AM, Fargusson.Alan <[EMAIL PROTECTED]>wrote: > If you have disk sitting around that you could add to the VG then why not > add them to the VG when you create it, and make the filesystems large enough > that they don't need to grow? > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Scott Rohling > Sent: Friday, August 15, 2008 9:11 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Root filesystem > > > If you're talking about a VG that has free space and a script smart enough > to add the free space and do the resize, etc -- then it sounds nifty and > not > too hard. > > If you're talking about getting VM to give you another minidisk, which you > then add to the VG and then add space to the LV -- that's a magnitude more > complicated (but certainly doable with things like REXECD on VM, vmcp to > link the disks, etc). > > But still - that would be nifty too :-) Interesting idea... > > Scott Rohling > > On Fri, Aug 15, 2008 at 10:04 AM, Mark Post <[EMAIL PROTECTED]> wrote: > > > >>> On 8/15/2008 at 12:58 AM, in message < > [EMAIL PROTECTED]>, > > Mark > > Perry <[EMAIL PROTECTED]> wrote: > > -snip- > > > Is there a way to trigger a script when a filesystem (FS) hits a > certain > > > percentage full? (90%?) > > > > Of course. I have such a thing set up on my Slack/390 development > systems > > so that I know when to temporarily suspend rsynching from my "upstream" > > source at slackware.com. > > > > > If so, then one could develop a method to automatically issue the > > > required lvresize and ext2online commands to keep the FS within a > > > certain percentage range (70-90%?). Of course rules could be developed > > > to make this more sophisticated: > > > which FS are controlled, what % range per FS, limits of VG % free etc. > > > > You're certainly willing to do that to yourself. I would not want to do > > it, nor make that available to others. That sort of thing is very, very, > > complicated, and I would want a human looking at that and making > decisions, > > not software. > > > > > > Mark Post > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > __________________________________________________________________________________________________ > > CONFIDENTIALITY NOTICE: This email from the State of California is for the > sole use of the intended recipient and may contain confidential and > privileged information. Any unauthorized review or use, including > disclosure or distribution, is prohibited. If you are not the intended > recipient, please contact the sender and destroy all copies of this email. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
