Increase the size of the disc + oracle datafiles

Similar Questions

• Impossible to drop the disc?

  env: 11.2.0.2.3
  
  I have a redundancy normal diskgroup (asm/RDBMS compatibility set to 11.2.0.0) containing two discs, it's everyone in own failgroup.
  I've tested the disk_repair_time attribute and took one of the disks in the group offline and waited until the expiration of the timer - to see if the disc - Oracle and test how I can recover from this situation if the drive was missing.
  
  Then I took the LOG2 drive off line and waited...
  
  ASM alerts log, I see:

  Fri Sep 09 09:59:21 2011
  WARNING: Disk (LOG2) will be dropped in: (168) secs on ASM inst: (1)
  Fri Sep 09 10:00:55 2011
  WARNING: Disk (LOG2) will be dropped in: (74) secs on ASM inst: (1)
  Fri Sep 09 10:02:27 2011
  WARNING: PST-initiated drop of 1 disk(s) in group 3(.467124207))
  SQL> alter diskgroup LOG drop disk LOG2 force /* ASM SERVER */
  NOTE: GroupBlock outside rolling migration privileged region
  NOTE: requesting all-instance membership refresh for group=3
  Fri Sep 09 10:02:29 2011
  GMON updating for reconfiguration, group 3 at 30 for pid 33, osid 13932
  NOTE: group LOG: updated PST location: disk 0000 (PST copy 0)
  NOTE: group 3 PST updated.
  Fri Sep 09 10:02:29 2011
  NOTE: membership refresh pending for group 3/0x1bd7bfef (LOG)
  GMON querying group 3 at 31 for pid 18, osid 10302
  SUCCESS: refreshed membership for 3/0x1bd7bfef (LOG)
  SUCCESS: alter diskgroup LOG drop disk LOG2 force /* ASM SERVER */
  SUCCESS: PST-initiated drop disk in group 3(467124207))
  NOTE: Attempting voting file refresh on diskgroup LOG
  NOTE: starting rebalance of group 3/0x1bd7bfef (LOG) at power 1
  Starting background process ARB0
  Fri Sep 09 10:02:34 2011
  ARB0 started with pid=37, OS id=14883
  NOTE: assigning ARB0 to group 3/0x1bd7bfef (LOG) with 1 parallel I/O
  Fri Sep 09 10:02:40 2011
  NOTE: GroupBlock outside rolling migration privileged region
  NOTE: requesting all-instance membership refresh for group=3
  Fri Sep 09 10:02:40 2011
  NOTE: stopping process ARB0
  SUCCESS: rebalance completed for group 3/0x1bd7bfef (LOG)
  Fri Sep 09 10:02:43 2011
  GMON updating for reconfiguration, group 3 at 32 for pid 38, osid 14888
  NOTE: group LOG: updated PST location: disk 0000 (PST copy 0)
  NOTE: group 3 PST updated.
  WARNING: offline disk number 1 has references (904 AUs)
  NOTE: membership refresh pending for group 3/0x1bd7bfef (LOG)
  GMON querying group 3 at 33 for pid 18, osid 10302
  SUCCESS: refreshed membership for 3/0x1bd7bfef (LOG)
  NOTE: Attempting voting file refresh on diskgroup LOG

  And from RDBMS alerts journal:
  

  Fri Sep 09 10:02:32 2011
  SUCCESS: disk LOG2 (1.2526490858) renamed to _DROPPED_0001_LOG in diskgroup LOG

  OK, check in asm v$ asm_disk:
  

  SYS@+ASM1 SQL>r
    1  select a.name "GroupName", a.state "GroupState",b.name,b.mount_status,b.header_status,b.mode_status,b.state "DiskState",b.repair_timer
    2  from v$asm_diskgroup a,v$asm_disk b
    3  where a.group_number = b.group_number
    4* order by a.name,b.name
  
  GroupName                      GroupState  NAME                           MOUNT_S HEADER_STATU MODE_ST DiskStat REPAIR_TIMER
  ------------------------------ ----------- ------------------------------ ------- ------------ ------- -------- ------------
  DATA                           MOUNTED     DATA1                          CACHED  MEMBER       ONLINE  NORMAL              0
  DATA                           MOUNTED     DATA2                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID3                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID4                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID_0001                      CACHED  MEMBER       ONLINE  NORMAL              0
  LOG                            MOUNTED     LOG1                           CACHED  MEMBER       ONLINE  NORMAL              0
  LOG                            MOUNTED     _DROPPED_0001_LOG              MISSING UNKNOWN      OFFLINE FORCING             0
  
  7 rows selected.
  
  
  SYS@+ASM1 SQL>select * from v$asm_operation;
  
  no rows selected

  So, why the disc always showing to v$ asm_disk if it fell? Or is it? I thought that Oracle should drop the disc at the expiration of the timer of the repair, but then why I always see it? I want to add the failed drive to return once again... How can I realize that, if the drive is still a member of the diskgroup of the NEWSPAPER?
  
  Thank you..
  
  Published by: AJ on 09.sep.2011 01:17

  Hello

  the reason behind this, is that a DISC will get status COWARD, if all valid content could be moved to another drive.
  However, in your case your LOG diskgroup consisted only of 2 discs (and 2 failgroups). So when access to a failgroup had disappeared, the whole failgroup was set to offline.
  Now when the repair timer expires the disks to be abandoned. However, it cannot be moved, because the data on the disk can not be moved to other disks.
  So what happens, is that your discs will be defined in the sense of "FORCING", as soon as the data can be rebalanced to another drive (maybe when you add a new drive), the drive really will be abandoned.

  Concerning
  Sebastian

• can I increase the size of disc can I burn in windows dvd creation.

  Right now I can burn only 1.5, as most of the disc I burned 4.5 GB, I was hoping to increase the size of dvd in the disc.

  Right now I can burn only 1.5, as most of the disc I burned 4.5 GB, I was hoping to increase the size of dvd in the disc.

  ==================================
  I was wondering... What is the length of your film? John Inzer - MS - MVP - Digital Media Experience - Notice_This is not tech support_I'm volunteer - Solutions that work for me may not work for you - * proceed at your own risk *.

• Discs ASM on EBS. Increase the size?

  Hello
  
  My apologies if this is in the wrong forum...
  
  In any case, I'm experimenting in the EC2 cloud. (After considerable bother...), I have a database of 11.2 oracle running with a pair of ASM starts. I decided to try and increase the size of one of my groups of disks.
  I couldn't really find ' how - to of "on this subject so decided to jump in full. I took the following approach.
  
  Closing database
  Disassemble the asm diskgroup
  detach the ebs volumes (there 6 in my diskgroup).
  snapshot volumes s3
  create new larger volumes of the photos above.
  attatch the new volumes
  -Here, the plan was to go back the asm diskgroup and finish.
  HOWEVER... it really happened that way.
  
  ORA-15017: diskgroup "RECON" can not be mounted.
  ORA-15063: ASM discovered an insufficient number of drives for diskgroup "RECCE".
  
  I kinda messed up with oracleasm, verification that he could see the disks etc., reload etc all without success.
  
  I restarted the server and, Lo and behold, all my starts returned. With the new volumes. I was going to congratulate me when I noticed that the diskgroup was still the same size as before!
  I tried a resizing of the disk group, but that did not help either.
  
  So, my questions are
  
  (1) how can I increase the size of the disks?
  (2) this valid approach is at all?
  (3) are there documents anywhere that tell me exactly how to perform this kind of operation?
  
  Thanks for your time.
  
  
  Ralph.
  
  Published by: user13024707 on February 5, 2011 08:44

  Maybe it's too late but here goes...

  ASM disk group can have volumes that differ in size.
  Add new volumes to the existing disk group.
  rebalance
  lower old smaller volumes that you want to resize.
  rebalance
  old volume is now out of ASM and can be delt with at the level of the OS to make it what you want.

  Repeat until all the old volumes have disappeared.

  re - integrate the new volumes once they have been rebuilt.

  All without interruption and ASM maintains all the data.

  It works best if you have enough new larger volumes to take all the data on the old volumes where you can drop all the old volumes at the same time.

• Increase the size of the disc does not completely.

  Recently, I noticed that a server was approaching the 600 GB HDD capacity.  If (as I did with other servers), I increased the size of the volume on the SAN.  vSphere found the climb.  Then, I was able to go into Disk Manager and I saw (unpartioned) free space on the server.  I expanded the volume without problem.  But when I go into windows Explorer, it still shows the old ability.  Since I've done it before on other servers, I'm a bit mixed upward.  I even restarted early this morning to see if he'll fix it, but it didn't.  So, I missed a step key somewhere?  Most of my other servers are windows 2008 R2... this one is windows 2008 standard... is there a problem because of this?  It seemed simple enough.  I did some preliminary research, this morning, but I could not find a definitive answer anywhere.  So, I thought I'd try everyone here.  Any ideas?

  Thank you

  Ryan Kotowski

  You can try the diskpart utility to extend the drive.

  Open the command prompt

  1 diskpart

  2 volume of the list

  3. Select the volume

  4 extend the file system

• Increase the size of the disc (thickness) guest operating system

  Hi guys,.

  New to ESXi invited 12 GB XP Pro, but now need to increase the size of the drive, I created. The size seems little gray (see below). As it is a type of customer not thin and drop thick, does that mean I can't increase the size of the disk?

  See you soon,.

  Declan

  Unfortunately, you can not increase IDE drive. It can be performed

  (1) as with a SCSI drive

  (2) when there are no snapshots

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• Increase the size of the tablespace: which of the data file for the tablespaces ine that I have to increase?

  Hello

  I need to increase the size of the tablespaces in EBS R12 Database 11.2.0.3.0:

  APPS_TS_TX_IDX

  APPS_TS_SEED

  APPS_TS_TX_DATA

  But they all have multiple datafiles:

  Example for APPS_TS_SEED:

  [data oracle@ebs122dev] $ of the hs - a_ref0 *.

  1, 5G a_ref01.dbf

  1, 2G a_ref02.dbf

  508M a_ref03.dbf

  2, 0G a_ref04.dbf

  2, 0G a_ref05.dbf

  2, 0G a_ref06.dbf

  Many of the datafiles should I resize to increase the size?

  Thank you

  Luis

  Hello

  It does not matter what file you resize.

  Personally, I prefer to start with the first file and reach the largest file size and resize then the following.

  In addition, having the files with a size that is a multiple of 1 GB is a good practice for me.

  Another option is to activate the autoextend for data files option.

  You can set the maximum size of 4 GB for example all files in storage areas that are growing rapidly.

  Kind regards

  Bashar

• Increase the size of the workspace

  Hello

  Please need your help because I'm completely confused how to increase the size of the workspace.

  I made a mistake by one of my workspaces 50 Mb instead on 500 MB, now I can not find any way in Apex to change this.

  Please help me understand the process, I guess it should be within the Apex Admin, but I can find it.

  Thank you very much

  Andrei

  Hi Andrei,

  aracila wrote:

  Hello

  Please need your help because I'm completely confused how to increase the size of the workspace.

  I made a mistake by one of my workspaces 50 MB on the 500 MB, now I can't find some way in the Apex to change that.

  Please help me understand the process, I guess it should be within the Apex Admin, but I can find it.

  Thank you very much

  Andrei

  The method mentioned by benhamdia and Jitendra is to make a service request and appoving it.

  This is done as follows:

  • Sign in your workspace as administrator of the workspace and make a service request to add storage. Maximum storage that can be added to the existing is 500 GB. Reference: http://docs.oracle.com/cd/E37097_01/doc.42/e35129/aadm_request.htm#AEADM144
  • Log in Instance of the Administration of the APEX and approve the service request. Reference: http://docs.oracle.com/cd/E37097_01/doc.42/e35129/adm_ser_rqst.htm#CIHFDCFJ

  But I'd rather make the DBA way as follows (to make this connection in sqlplus with the sys and privilege sysdba user):

  • Determine the name of the file and the size of the associated workspace schema table space:

  select file_name,tablespace_name,bytes/1024/1024 as MB from dba_data_files;
  

  Assume that storage space is "APEX_25383616320599297" and the name of the file is "/ u01/app/oracle/oradata/orcl/APEX_25383616320599297.dbf".

  • Resize the tablespace to the selected size:

  alter database datafile '/u01/app/oracle/oradata/orcl/APEX_25383616320599297.dbf' resize 500m;
  

  In addition, rather than create the schema when creating workspace, I prefer to create tablespace, then create a schema associated with the table space manually (as there is more control over the options during the creation of tablespace or schema).

  After you manually create the schema and the tablespace, just associate the schema for the workspace while creating the workspace.

  I hope this helps!

  Kind regards

  Kiran

• Big increase in size of the backups after upgrade

  Hello

  I updated my database of 10.2.0.4 on win2003 SP2 for 11.2.0.1.0 SE SE on win2008 R2 SP1 64 - bit, by making exp/imp

  The amounts of size databasefiles up to approximately 150 GB on each server

  But when I do a normal RMAN backup of the data files to the new database (database backup device type disk); I get a backupset that is 78 GB in size.

  On the old database, the backup size was only 36 GB

  Two data are substantially the same, and I don't think I'm using the compression on any one of the database backups. I listed the RMAN settings below

  Can someone tell me why I see this huge increase in size of the backups?

  Best regards

  Klaus Mogensen

  10 GB RMAN settings:

  CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE the FORMAT of DISC TYPE CHANNEL DEVICE "C:\backup\vtrack\backupset\ora_df_%Y_%M_%D_%T_%t_s%s_s%p.bkp";

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFVTRACK. ORA'; # by default

  11g RMAN settings:

  CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' E:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFVTRACK. ORA'; # by default

  That is why,

  Configuring your channel 10g device:

  SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE

  Configuring your channel 11g device:

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  The 11g, 10g being compressed backups are not.

• ADF: How to increase the download size of af: inputfile

  Hi all

  I'm new in the ADF and use 12.2.1. I use af:inputfile to download the csv file in the database. It works very well with a small amount of data. But when I download a large file it shows me the error message as below:

  

  It is possible to increase the size of download of af: inputfile. Its urgent assistance please.

  Thanks in advance.

  Kind regards

  The maximum size of files that can be downloaded is configured in the web.xml file. the doc:

  Configuration

  Because ADF Faces will temporarily store the files by default, incoming (on disk or in memory), it limits the size of acceptable incoming requests to avoid denial of service attacks that could try to fill a memory disk or a flood lasts with downloaded files. By default, only the first 100 kilobytes in any query will be stored in memory. Once that has been completed, will serve as disk space. Yet once, by default, which is limited to 2 000 kilobytes of disk space for a request for all of the files combined. Once these limits are exceeded, the filter will throw a EOFException . By default, files are stored in the temporary directory used by java.io.File.createTempFile() , which is generally defined by the system property java.io.tmpdir . Of course, this will not be sufficient for some applications, you can set these values using three of servlet context initialization parameters:

  oracle.adf.view.faces.UPLOAD_MAX_MEMORY

  512000

  oracle.adf.view.faces.UPLOAD_MAX_DISK_SPACE

  5120000

  oracle.adf.view.faces.UPLOAD_TEMP_DIR

  / tmp/aDFUploads /.

  Timo

• Is it possible to increase the size of attachments?

  We use the 11.1.1.6 version (ps5) Oracle for our developments.  Is it possible to increase the size of attachments in the workflow?  We changed the

  org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE values in the web.xml file? But it did not work. Is it possible to increase by more than 10 MB?

  It worked... Oracle BPM project is the web.xml file in the WEB - INF folder... When you set the

  org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE,

  org.apache.myfaces.trinidad.UPLOAD_MAX_MEMORY,

  org.apache.myfaces.trinidad.UPLOAD_TEMP_DIR

  We can achieve what we wanted.

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Publish with the increase in size of the readers

  Hi all

  I have a seemingly common problem, but unfortunately common solutions do not seem to apply.  I have a VM that I migrated to ESXi 4 5.1 a year ago and have used without problem.  Recently, it has become necessary to increase the size of main drive of the 60 GB original but the size options are grayed out.  I checked and it is y no snapshot files or y at - it hard < 0000 files > in the directory of the virtual machine in the data store.  I even created a new snapshot, then used the "clear all" button to make sure that all of the snapshots are gone, but the size options are still grayed out.  I tried the upgrade virtual hardware then in the VM properties, I see that the version is vmx-09 that I understand is the latest version.  The disk is a thick accrued lazy set to zero that I thought that maybe part of the problem, so I added a new thin provisioned disk and I can't increase the size of this one either.  It seems to be limited to this virtual machine, but as I have other VM is present on this server I can increase the size of the disk without any problem even if I have not updated the virtual hardware for those so that they are always to version 7 (I don't know if this matters).

  So I'm quite positive, there is no snapshot or snapshot files, I updated the latest material available, and I'm sure that the type of disc is not serious because it seems to apply to thin provisioned and drop discs thick.  I'm out of ideas.  Any help would be appreciated!

  Kind regards

  Tim

  Hi Tim,.

  Have you tried to add additional SCSI disk (which adds the controller and drivers needed). Do a clean reboot then switch your IDE to SCSI and if successful (after other clean reboot) remove the new drive that you have added. By doing this, you are making sure the drivers for the controller are installed before switching types.

  See you soon,.

  Jon

• Increase the size of disk problems

  I just upgraded from Fusion 4 to 5 in preparation for the upgrade of Windows 7 to 8.  When I initially installed my VM several months ago, I waited to invite me on the amount of disk space, I wanted to allocate, but he never did the installation.  He created the virtual machine of 20 GB (boring), which would work if Windows ever wanted to do an update and that you ever wanted to save a file to the virtual computer.

  I used the Fusion to increase the size of the disc to 122 GB (I have over 600 GB available on my Mac) and it is distributed correctly and when I open windows the space was available on drive C.  However, when I discovered the virtual machine to the Virtual Machine in Fusion library it reads 20 GB.

  After more than an hour of reading of the VMWare knowledge base, I found an article that said that I had to increase the disk using Mac disk utility; However, this option is disabled/grayed out for me.  Another article proposed a ton of utility downloads to do this and overall I am lost.  It would be completely avoidable BS if the installation would have helped clarify the size of my disk on the installtion of the virtual machine.  Alas, it's wasn't the case.

  My question is does my windows hard disk shows 122 GB total space, but the library of virtual machines VMWare shows correct 20 GB and what can I expect if I start tyring upgrade to Windows 8 in terms of space?  Is there allocated 20 or 122 GB?

  Thank you.

  I just upgraded from Fusion 4 to 5 in preparation for the upgrade of Windows 7 to 8.  When I initially installed my VM several months ago, I waited to invite me on the amount of disk space, I wanted to allocate, but he never did the installation.  He created the virtual machine of 20 GB (boring), which would work if Windows ever wanted to do an update and that you ever wanted to save a file to the virtual computer.

  IIRC A Windows 7 Virtual PC to a 40 GB in VMware Fusion 4.x by default however any default size one can always modify virtual hardware parameters before installing an operating system.  Anyway to increase the size of the virtual hard disk is a process in two stages, the first of which is made in the settings of the Virtual Machine's hard drive.  The second part is made with a 3rd party utility or the OS itself, when it is necessary and it is applicable in the case of Windows 7.

  In Windows 7, just go to disk management and extend the Volume, he tries but a few seconds.

  Note: Before performing any disk level operations such as this should ensure that you have a clean backup * of the entire Virtual Machine.

  =========

  * It is a known fact that Time Machine is not 100% reliable backing up/restoring VMS in all circumstances/conditions.  Also back up Virtual Machines via Time Machine of disk/time intensive and wastes a lot of space for something that may be corrupted and worthless time to restore it.  At least I would exclude the Virtual Machines with virtual machines and Time Machine shutdown, not suspended and VMware Fusion closed and then manually copy the VMS to another location, preferably on a different physical hard drive.  So keep the user data stored in the virtual machine saved out of the Virtual Machine on a regular basis in order to always have a backup of the current user data.  If you need to restore a properly saved by VM is not as common at least you will have a virtual working Machine and data user to go forward with when you find out your Time Machine backup of the virtual machine fails.

• Reduce the size of the disc put into service

  We have accidentally increased a record of 600GO and approved the change, but the expansion of the disc has not been validated in the operating system.

  I need the rear disc, is possible or do I need to create a new vDisk, restore the data on it and remove the one that is now oversized.

  See you soon!

  Brendan

  Hi Brendan,

  You must use the VMware Converter and you can change the layout of the destination VM in the next page.

  

  You may decrese the size in the menu size/capacity.

  You can use the link below for more information, order 2 method:

  http://vSphere-land.com/tips-tricks/re-sizing-virtual-disks

  It will be useful.

  NetRock,