Disk Partition Sizes - Best Practices

In the old days of SunOs 4.x we used to spend a lot of time figuring out disk slice sizes to make sure that we maximized the space on the old 200 meg disks.
Then once we started using the 1 to 4 gig disk we used just make it one big slice and not worry about things filling up because when it was full, it was full.
Now, we have these huge 32 gig to 100+ gig drives and things become tricky again. I was wondering how other large companies are slicing up their drives and what thie best practices are.
The size I was interested in were for:
8,18,36,72,146 G disk
My thought is that the 8 gig is still small enough to do the complete disk, but the others may need some thought.
If some people could let me know what they do for:
/var
/opt
/usr
I know that we should handle non DB machines different than DB machines so any advice on that would be great.
Thanks in advance.

well normally when I setup systems I don't like /usr or /var or anything so I lump everything into root "/", since you don't have any other filesystems your space dun get "locked" and wasted it also makes it easier to do manual backups like ufsdumps also.
But if you do want to partition the exception would be /var and /opt as a lot of patches and software normally defaults to these 2 as the base installation directory but as I said normally I throw everything into "/".
Then there's slice 2, 3, 4 and 7 which normally I don't install anything on them
slice 2 is "backup" represents the entire disk, it can be used but normally nobody touches this. if you use it, I think there will be a problem if you wanna do things like 'dd'
not sure now but In the old days when you used things like volume manager, vm will take slice 3 and 4 as a private/public region if you have data on it prior to encapsulation it will move the data to other slices for you, but if there are no free slices to move data to from slice 3 and 4 then vm install will fail or if you want to unencapsulate the rootdisk later on you will have a confusing problem as orignally your data from slice 3 and 4 was moved elsewhere during vm encapsulation.
slice 7 by default with I first install os I will either leave it blank for future or allocate 10mb to it, this is in case I wanna mirror the disk using disksuite so I normally designate slice 7 of all the disks as my metadb, if you use up all the space and leave slice 7 blank you can still allocate space to it for metadb by allocating a few sectors to it from the "swap" area in cdrom single user mode.

Similar Messages

  • ASM on SAN datafile size best practice for performance?

    Is their a 'Best Practice' for datafile size for performance?
    In our current production, we have 25GB datafiles for all of our tablespaces in ASM on 10GR1, but was wondering what the difference would be if I used say 50GB datafiles? Is 25GB a kind of mid point so the data can be striped across multiple datafiles for better performance?

    We will be using Redhat Linux AS 4 update u on 64-bit AMD Opterons. The complete database will be on ASM...not the binarys though. All of our datafiles we have currently in our production system are all 25GB files. We will be using RMAN-->Veritas Tape backup and RMAN-->disk backup. I just didn't know if anybody out there was using smallfile tablespaces using 50GB datafiles or not. I can see that one of our tablespaces will prob be close to 4TB.

  • Lun Size best practice for UC apps and VMWare?

    Hi,
    We have UCS manager v2.1 with FI 6248 direct FC attached to NetApp with plenty of storage.
    Per following doc, Lun size for UC apps should be 500GB - 1.5TB and 4 to 8 VMs per Lun.
    http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements#Best_Practices_for_Storage_Array_LUNs_for_Unified_Communications_Applications
    We have four B200M3 blades and 3 to 4 UC apps (CUCM, Unity, UCCX) will be hosted on each blade. May add more VM the blades in the future.
    I am thinking four 1 TB Luns and one for each blades. (actually 8 Luns in toal, 4 boot luns for ESXi and 4 for UC apps).
    What is the best practice (or common deployment) to create Lun size and design?
    Thanks,
    Harry

    UC apps need low IO，nothing special，Reference vmware LUN design is ok.

  • Increase System Volume/Startup Disk Partition Size

    Hi,
    I don't know much about Macs or OSX so bear with me.. I have been searching for a simple way to increase the size of the System Volume on my daughters MacBook running Maverick. She keeps getting a warning to say that the start-up disk is full or nearly full. I have used drive magic to clear some of the temp files and also used monolingual which has helped.
    The trouble is that the System Volume only has 74 MB of free space whilst the User Data partition has 172GB of free space. I have tried to clean the disk using utilities and have moved the User folder to the User Data partition but that is not really helping..
    Is there a way to expand/extend the System Volume area so that it doesn’t constantly run out of space without losing the User Data?
    I can’t update applications because if I try I get told there is not enough disk space available…
    I have uploaded some screenshots that may help:
    System Volume:
    https://dl.dropboxusercontent.com/u/7548959/sv.jpg
    User Data:
    https://dl.dropboxusercontent.com/u/7548959/ud.jpg
    If there is some software that I can purchased that could be used to do this then let me know.
    Cheers
    M

    Everything there looks ok in that screenshot (I was looking to see if there was any [Backup] data, but you only have 400MB in the User Data partition)
    I would suggest that you just have one partiton (usually named Macistosh HD, but you can name is anything you want. (Is there a reason why you have it partitoned this way?)
    To expand the System Volume partiton, you first need to delete the User Data partiton.
    BACK UP ALL DATA
    Copy all files from the User Data Partion to an external HD (or flash drive)
    In Disk Utility, select the Partiton Tab, click the User Data Partiton and click [-] to Remove
    Drag the Right Corner of the System Data partiton to expand the partiton
    OPTIONAL
               a) Click [+] to Add Back the User Data partiton
               b) Move the slider between the partitons to re-size
        6. Click [Apply]
        7. Copy back the User Data from the External Drive (or flash drive]
    For more info see: Disk Utility - Add, Delete, and Resize Existing Volumes

  • Increase startup disk partition size

    Greetings,
    I need a simple way to increase the size of my startup drive.  Currently my SSD drive has 2 equal partitions of approximately 250GB.  The top partition has no data or applications, it is empty and can be eliminated.  The lower partition is 95% full with applications only.  The operating system is 10.8.5.
    Can I simply copy everything from my Home Folder (all my applications and operating system) to a secondary drive, then reformat the impacted original startup drive to one partition, then copy the Home Folder back?  Will the operating system work properly?  Will applications work properly?  Sorry for these basic questions, but I would sincerely appreciate any knowledge on this topic.
    Thanks, Scott

    Use a program such as the Disk Utility, Carbon Copy Cloner, or SuperDuper to clone the contents of the bottom partition to the top one, restart from the top one, delete the bottom one, and then resize the remaining partition to the size of the drive.
    If your computer is authorized to play protected iTunes Store content, deauthorize it first.
    (91890)

  • JDialog size best practice

    I am looking for the best way of correctly sizing a JDialog. The problem I am running into is that I have an application that runs on both Windows XP and Windows 2000. Windows XP apparently has a taller title bar than Windows 2000, so the bottom portion of my dialogs are getting cut off on Windows XP because I have been specifying the based on my Windows 2000 machine. Additionally, users with large text enabled also see the problem despite the version of Windows. Am I missing an obvious solutions, or do I need to try to determine what version of Windows the user is on and whether or not they have large text enabled before setting the size of the dialog? Thanks for any assistance.
    Derek

    Hello Derek,
    do I need to try to determine ... whether or not they have large text enabled?I'm afraid yes. And this can be done from within Java only with JNI. The feature is probably seldomly used, but the titlebar of the Windows-windows is user definable. Right-click on the desktop, go to settings, then a tab called somewhat like "view" (Darstellung), open the Image element comboBox and click "title bar of an active window". There you can see that you may set the size from 18 up to 100 pixel.
    Regards
    Joerg

  • WEBI Report Size Best Practices

    What are some standards (measured in time, records and db size) for the following for WEBI reports on BW Universes -
    1 - when run on demand
    2 - when scheduled to create an instance
    We are looking for some baselines.  For example: <5 mins for on demand and <15 mins for scheduled, etc

    Hi Subham,
    If you are looking for the size of the WID file, you can get this through the InfoObject.
    Please note that this WID file only changes if the WebI document was actually saved.
    Below is a sample code snippet that will retrieve the file size from an InfoObject:
    IInfoStore boInfoStore = (IInfoStore) boEnterpriseSession.getService("InfoStore");
    String query = "SELECT SI_FILES FROM CI_INFOOBJECTS WHERE SI_INSTANCE='false' AND SI_NAME='" + webiDoc + "'";
    IInfoObjects boInfoObjects = boInfoStore.query(query);
    if (boInfoObjects.size() > 0) {
         IInfoObject boInfoObject = (IInfoObject) boInfoObjects.get(0);
         IFiles boFiles = boInfoObject.getFiles();
         IFile boFile = null;
         for (int i=0; i<boFiles.size(); i++) {
             boFile = (IFile) boFiles.get(i);
             out.print(boFile.getName() + ": " + boFile.getSize() + "<BR>");
    } else {
          out.print("No WebI document found!");
    Hope this helps.
    Regards,
    Dan

  • Adobe DPS Android - Folio Size Best Practice

    Hey everyone,
    we designed a magazine for iPad and now want to bring it over to Android. A little bit of research and it seems, that the Samsung Galaxy Tab 7' is one of the most popular tablets. Second to that is the 10' Samsung Galaxy tab.
    The problem I know have is, for which resolution I should re-do my magazine to work on most android devices.
    I read about it (http://blogs.adobe.com/indesigndocs/2012/10/creating-dps-folios-for-android-devices.html), but still would be happy to hear from you guys regarding the following things:
    Would it be wise do set a new folio size 1280x800 (to cover the 10')? I think it will be automatically scaled down to 7' on smaller tablets, right?
    Or is it the better approach to work with an addiotional folio size 1024x600 to target the most popular tablet with 7'. As I recall correctly, the content will not be enlarged on larger tablets like 10', right?
    What if I have a retina-Android-Device. Does the folio automatically scales up like on iPad?
    Personally I would think that approach 1 is the one which makes most sense. content will be displayed fine on 10' and 7' with content slightly smaller on 7' (just like iPad retina and iPad mini).
    What do you guys think?
    Thanks a lot in advance!
    florian

    We starting to test publish to Android. Our 1024x786 PDF iPad edition is showing OK on content viewer for android. There is black boarders, but with pich and zoom, it's perfectly viewable. HTLM and web content works fine. We simply don't have the time to recreate folios at various sizes. So our solution works for us.

  • Best practice for partitioning 300 GB disk

    Hi,
    I would like to seek for advise on how I should partition a 300 GB disk on Solaris 8.x, what would be the optimal size for each of the partition.
    The system will be used internally for running web/application servers and database servers.
    Thanks in advance for your help.

    There is no "best practice" regardles of what others might say. I depends entirely on how you plan on using and maintaining the system. I have run into too many situations where fine-grained file system sizing bit the admins in the backside. For example, I've run into some that assumed that /var is only going to be for logging and printing, so they made it nice and small. What they didn't realize is that patch and package information is also stored in /var. So, when they attempted to install the R&S cluster, they couldn't because they couldn't put the patch info into /var.
    I've also run into other problems where a temp/export system that was mounted on a root-level directory. They made the assumption that "Oh, well, it's root. It can be tiny since /usr and /opt have their own partitions." The file system didn't mount properly, so any scratch files in that directory that were created went to the root file system and filled it up.
    You can never have a file system that's too big, but you can always have a file system that's too small.
    I will recommend the following, however:
    * /var is the most volatile directory and should be on its own several GB partition to account for patches, packages, and logs.
    * You should have another partition as big as your system RAM and assign that parition as a system/core dump for system crashes.
    * /usr or whatever file system it's on must be big enough to assume that it will be loaded with FOSS/Sunfreeware tools, even if at this point you have no plans on installing them. I try to make mine 5-6 GB or more.
    * If this is a single-disk system, do not use any kind of parallel access structure, like what Oracle prefers, as it will most likely degrade system performance. Single disks can only make single I/O calls, obviously.
    Again, there is no "best practice" for this. It's all based on what you plan on doing with it, what applications you plan on using, and how you plan on using it. There is nothing that anyone here can tell you that will be 100% applicable to your situation.

  • BEST PRACTICE TO PARTITION THE HARD DISK

    Can some Please guide me on THE BEST PRACTICE TO PARTITION THE[b] HARD DISK FOR 10G R2 on operating system HP-UX-11
    Thanks,
    Amol
    Message was edited by:
    user620887

    I/O speed is a basic function of number of disk controllers available to read and write, physical speed of the disks, size of the I/O pipe(s) between SAN and server, and the size of the SAN cache, and so on.
    Oracle recommends SAME - Stripe And Mirror Everything. This comes in RAID10 and RAID01 flavours. Ideally you want multiple fibre channels between the server and the SAN. Ideally you want these LUNs from the SAN to be seen as raw devices by the server and use these raw devices as ASM devices - running ASM as the volume manager. Etc.
    Performance is not achieved by just partitioning. Or just a more memory. Or just a faster CPU. Performance planning and scalability encapsulates the complete system. All parts. Not just a single aspect like partitioning.
    Especially not partitioning as an actual partition is simple a "logical reference" for a "piece" of the disk. I/O performance has very little do with how many pieces you split a a single disk into. That is the management part. It is far more important how you stripe and whether you use RAID5 instead of a RAID1 flavour, etc.
    So I'm not sure why you are all uppercase about partitioning....

  • Best practice of expanding partition size

    Hi,
    I am just wondering what's the best practice of expanding a partition. Currently the server I am working in has the partitions configure as below:
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/mapper/VolGroup01-LogVol00
    5046848 4630796 155548 97% /
    /dev/sda1 101086 50293 45574 53% /boot
    tmpfs 4087296 2388360 1698936 59% /dev/shm
    /dev/sda3 5162828 141544 4759024 3% /tmp
    /dev/sdb1 1923068 734956 1090424 41% /fs0
    /dev/sdb2 1923084 70908 1754488 4% /fs1
    /dev/sdc1 89406276 68095788 16768916 81% /fs2
    /dev/sdc2 13804204 7061912 6041056 54% /fs3
    /dev/sdb3 6474880 4509556 1636416 74% /fs4
    Let's say I want to increase /fs2 which is /dev/sdc1 by another 15GB. I can go into the VMware and increase the disk size by 20GB but how will I go about increasing the partition size without affecting other partitions?
    Most of the instructions I see online basically creates a new partition but I want to avoid creating a new partition. So is it possible to do it?
    Thanks.

    You cannot increase a partition on a disk without affecting other partitions on the same disk unless it is the last partition. You will have to completely re-organize your partitions and restore from backup. You can however extend partitions that are under LVM control by adding a free LVM controlled partition or disk and assign it to any existing LVM volume in order to increase it's capacity. There is plenty of documentation and info available on the web. If you plan to increase your LVM root volume you need to boot form external media.
    Since you are using VMware there is actually no need to create multiple partitions on any disk. You can simply put each partition on it's own virtual disk. Then after you increase the underlying virtual disk, you can use "lvextend" for devices under LVM, or "gparted" to modify the partition, and use the "resize2fs" command to adjust the file system, even while the mounted volume is online.

  • Best Practices To Size the Datafile on ASM in Oracle 11gR2

    Hi DBAs,
    I need to know that what should be the datafile next extent on ASM. I have created a database 11gR2 with ASM. Now some certified DBA told me to create the datafile as small as possible and make it auto extend with the next extent size 1M. The expected data growth every month is about 20-25 Gig.
    Please let me know what are the best practices while for sizing the datafiles and extents in 11g using ASM. Any good document/note refer would be great help.
    Thanks
    -Samar-

    Hi Samar,
    I need to know that what should be the datafile next extent on ASM. I have created a database 11gR2 with ASM. >Now some certified DBA told me to create the datafile as small as possible and make it auto extend with the next >extent size 1M. The expected data growth every month is about 20-25 Gig.
    Please let me know what are the best practices while for sizing the datafiles and extents in 11g using ASM. Any >good document/note refer would be great help.I don't think there is any kind of recomendations for that, at least, I've never seen. As You probably know, ASM already divides the ASM files (any sort of files written in a ASM diskgroup) in extents and those extents are composed of AU. So, doesn't matter the datafile size, ASM will balace the I/O on all ASM disks in a diskgroup.
    I guess this thread ( AU_SIZE and Variable Extent Size ), even not being the subject of Your question, Will help You.
    I do believe there are more important factors for ASM performance, like stripe size, LUN size, storage configuration, etc.
    Hope it helps,
    Cerreia

  • Disk Utility -- Smallest (minimum) partition size

    I viewed an earlier discussion on this topic that was answered incorrectly, but I couldn't add this information to it because it had already been archived. However, I was unable to find it anywhere else on the web, so I thought it important to get on the record.
    Disk Utility in Leopard DOES enforce a minimum partition size. It is 1GB.
    This is documented in the Apple Service Training course "Leopard Tools and Techniques."

    V.K. wrote:
    it looks like DU will not allow you to create a partition smaller than one tenth of the disk size.
    when i do it on a 200GB drive the smallest size it let's me make is 20Gb, and for a 500GB drive it's 50GB.
    I guess that's a safeguard against creating too many partitions.
    Message was edited by: V.K.
    I thought so. Like most filesystems, all the information must be stored in the bootsector or whatever it's called with BSD, and the total number of files is related to the sizes and total numbers of partitions, so like FAT32 or even NTFS, HFS has it's practical and theoretical limits.
    I believe HFS has two bootrecords or equivalents, one for backup and this adds to the storage space issue.
    Going back to the old 1.44MB floppies, the unformatted size was over 1.7 MB and Norton and MS took advantage of that, but not all disk readers were happy with what they did. MS once shipped Windows on a set of 1.7 MB floppies. Of course this was BC (before CDs).

  • HT4818 What is the best Partition size for a windows 7 Home Premium. I'm trying to install Windows using Boot camp

    What is the best Partition size for a windows 7 Home Premium. I'm trying to install Windows using Boot camp

    Go into your system preferences and click the startup disk icon then select your Mac HD. 

  • Changing the size and/or erasing a disk partition

    I have a 2010 MacBook Pro with two disk partitions. The original is 100G and runs Mavericks, and the other is 200G and runs Snow Leopard.  I can change the size of the partition with Snow Leopard that I created but not the original.  In the end I need the partition running snow leopard to be 100G and the original with Mavericks to be 200G.  Essentially swap the size.  Do I need to erase the partition I created to change the size of the original.  If so, what is the best way to do this?

    This is Apple's guidance on disk partitioning.
    http://support.apple.com/kb/PH5845
    Barry

Maybe you are looking for