Mark Post wrote: >>>> On 8/14/2008 at 8:26 AM, in message <[EMAIL PROTECTED]>, > Ryan McCain <[EMAIL PROTECTED]> wrote: >> Thats the issue we are trying to avoid if possible. If we could put /, /opt, >> /usr, /lib, etc. etc. into LVM, we won't have to guestimate how much disk >> we'll need from the outset. We could grow as needed. > > Laid out properly, / will never grow. > > # df -h > Filesystem Size Used Avail Use% Mounted on > /dev/dasda1 388M 168M 200M 46% / > /dev/mapper/vg01-home 97M 4.4M 88M 5% /home > /dev/mapper/vg01-opt 74M 21M 50M 30% /opt > /dev/mapper/vg01-srv 1.2G 1.1G 100M 92% /srv > /dev/mapper/vg01-tmp 291M 34M 242M 13% /tmp > /dev/mapper/vg01-usr 2.0G 901M 1.1G 45% /usr > /dev/mapper/vg01-var 2.0G 608M 1.3G 32% /var > > Of course the amount of space dedicated to each LV will vary according to > specific needs. The fundamental concept is the same, and will (hopefully) be > the default on SLES11 if things go as I hope. > > > Mark Post > Is there a way to trigger a script when a filesystem (FS) hits a certain percentage full? (90%?)
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. Hint to distros: If such a method were available during the installation process then we would not need to make guesstimates of the LV sizes, they could be set small and allowed to grow as packages were installed. If a good idea..... then maybe add this to LVM2 so that the whole process was synchronized without the possibility of a FS becoming full (based on rules of course). mark ---------------------------------------------------------------------- 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
