Virtual Disk mis-reporting available size

I have a virtual disk on my 6140 that has a total capacity of 4 TB. It has a configured capacity of 2 TB. However, it says that my maximum volume size is only 107 GB. Where is my other 1.83 TB? I had a 1.9 TB volume on this virtual disk that I deleted last week. It seems that it still thinks it is there. Any suggestions?

I do not think you can use DU for resizing if you used a linux disk utility before. I never could do that, but am ready to learn how to do that.

Similar Messages

Disk Utility: Reporting wrong size for disk after a restore

First up, hardware is G4(PPC) running OS 10.4.11
I've just purchased and installed a new 500G drive for this old workhorse as an upgrade for the previous secondary drive. Set it up with a single partition, JHFS+. No problems so far. Went to copy the files from the old drive to this new one and thought, "Why don't I try that handly looking Restore button?". +Yeah, apparently a bad idea+. The old drive is 120GB. I set its (only) volume to be the source and my newly created partition to be the target; set it going and left it alone. All appeared to be well when I came back, until I checked the available space on the new drive.
Disk Utility now reports that this new, 500G drive has a Total Capacity of 128G (137,438,952,960 bytes).
*Remedies tried so far:*
- I've tried reformatting/partitioning, but wasn't able to convince it otherwise. Also tried it booting from an install DVD just in case that made a difference.
- I downloaded a utility from the drive manufacturer which I managed to get on to an ancient, dusty w2k box. Reformatted the drive with 2 NTFS partitions. This seemed to do the trick as they both mounted when I rebooted the Mac. However, when I went to reformat the volumes to JHFS I noticed that the total disk size was still being reported as 128G. Still, they reformatted fine and I transfered my data to them. On a reboot, though, the Mac decided that it didn't want to see the second partition and only shows me disk1s10, ignoring the second partition I set up.
- I have an identical, empty drive to the 500G. I thought I might be able to use the Restore "feature" to trick it back. Set up the second 500G in a firewire box, ran the restore from the empty volume to the screwed up one. No dice.
I thought that OS X ignored any sort of BIOS info on a drive and merely looked at the physical media. Is this correct? Does it store this gathered info in a file somewhere that I can delete?
*This is a call for help.*
I have no problems playing with the command line as root, if that's the sort of suggestions you've got. I just thought I'd ask here before I fdisk/dd etc from new500 to old500. Geometry of the new500 is 60801/255/63.

Thanks! That sounds like a good short term solution for a backup.
EDIT: Cross reference link for anyone who happens to google this thread with a similar problem:
http://discussions.apple.com/thread.jspa?messageID=7230072&tstart=0
Message was edited by: mr_lunch

Disk utility reporting wrong size drive

I have a Macbook 4,1 with an 120GB Hard drive. The hard drive has 3 partitions:
12GB Linux Partition
100GB OSX Partition
1GB Linux Swap Partition
It also has 7GB of Free Space at the end of the drive
Now I want to shrink the OSX Partition down to around 80GB (It has 30GB available space) so I have 27GB of Free space to create a Windows Partition. The problem is when I go into disk utility it reports the above partition structure but it also reports I have "100.3GB Free space" at the start of the drive. This is obviously incorrect. It seems harmless enough but the problem is it causes a "The chosen size is not valid for the chosen filesystem" error when I try to resize the OSX partition because the system adds up the size of all of the partitions, realises it's 220GB and so throws the error because it's above the 120GB Drive size. I can't seem to get it to realise that there is no free space at the start of the drive. I've tried using a couple of Linux partitioning programs like GParted and they recognise the correct partition structure but they had a couple of unrelated problems.
Does anyone have any ideas how I can get Disk Utility to sort itself out?

I do not think you can use DU for resizing if you used a linux disk utility before. I never could do that, but am ready to learn how to do that.

Understanding Virtual Disks and Sparse Allocation

1. From the doc here , i understand that allocation is fast when "Sparse Allocation" is used while creating a virtual disk and is slow when using non-sparse allocation. But does this mean that we are just talking about allocation alone? i.,e a one time activity - creation.
2. If my repository has 1TB space , then i see that i can create 'n' Virtual Disks each with a size of more than a 1TB(i.e, lets say 3-4 VDisks each with a size of 1TB); whereas, if i use non-sparse allocation, then i have to have the sum of the sizes of the disks to be lesser than 1TB.
FYI : I get an error if i allocate more than the space available: "OVMRU_002032E Excl-BigRepos - Repository size not large enough for new virtual disk of size: 999,999,999"
3. When i install OVS on a RAID-1 partition(with two virtual disks - say 100GB and 400GB), then, OVS picks up the 100GB disk by default and installs in there. And this 100GB is not 'visible' henceforth. Reasons?

1. Correct. Spare allocation means as the data is written the disk is expanded. This means, you're doing two operations as opposed to one with non sparse allocation. Thus, when writing to a virtual disk with a sparse allocation, the "write" could take longer if the disks doesn't have free space available.
2. Too a degree.... Yes. It depends on what storage you're using. On some storage, using compression and deduplication, this is not entire accurate. But, this is independent of anything to do with Oracle VM. Many storage environments now use "virtual allocation".
3. The default "LUN" used by by OVS can not be used for anything else. It is reserved. You will not able to use any free space on that LUN. The OVM manager expect "raw disks/LUN/shares" to used as storage. Such storage my be free of any filesystem, partition or etc. The Pools and repos necessary to run Oracle VM use a ocfs2 filesystem.

Disk Manager/Virtual Disk Manager Problem

I have an apparently working NAS drive that I can see, read. write to, and whatever as normal.
However backup/restore software cannot find the drive while Disk Manager shows it as "unknown" and "Not initialised" and Virtual Disk Manager reports it as "The Device is not Ready!"
Obviously with Virtual Disk Manager not finding it I cannot initiate it.
As I need to access the drive with a backup and restore prog does anyone know where I can go from here?

Hi,
Did you run Windows in a VM?
Please start virtual disk service and set its startup type as "Automatically".
Afterward, re-connect the drive into the computer for test. Remember to right click the disk and click to initialize disk.
If the issue still persists, please upload the disk management snapshot as below:
Karen Hu
TechNet Community Support

Finder is not correctly reporting available disk space

finder is not correctly reporting available disk space
my drive is 50% full but finder shows there is only @ 35% left
the difference is more than anything needed by the system
any ideas on what is causing the problem?

Try this:
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Disk utility reports smaller hard drive size than actual

I have been using a 3tb external drive (Formatted mac osx journaled) without any problems on my mac mini. Suddenly, it no longer allows me to write to the drive and more often it does not even recognize the drive when it is in the caddy. The caddy supports USB3 and is fairly new. The hard drive is a 7200rpm seagate.
When looking at the drive in disk utility, it states that the drive is 2.2 TB while the size is 3TB.
Does anyone have similar problems? Any recommendations?
Currently on OS X version 10.8.5.
Thanks!
When I insert the drive in the caddy I get the error message that it is not readable. Disk utility reports it as 2.2tb. The drive is a 3TB Seagate.

Hi Eric,
Can't really hook it up directly to a mac mini as the mini is pretty sealed. I did connect it to a PC as I wanted to run SpinRite on it and SpinRite gave me an error message that the Drive Size reported was less than the actual physical drive size.
SpinRite recommended not to perform any actions on the drive due to this discrepancy.
Not sure where to go at this point.
I could try to re-format the 3TB with OS X Journal and see if I get the 3tb back...

Shrink size of virtual disk

Hi,
I converted physical server to virtual machine using P2V method. Now I have 150GB virtual disk which has linux host and data is consuming only 30GB, the rest is free. What would I like is to shrink vdisk size to, lets say, 40GB because I don't need any more space. Is there any way to copy only data to another vdisk within OracleVM or shrink size of the disk without losing data?
Thanks.

Hi, thx for help, I finally did it.
Steps:
1. Boot up VM that needs to be shrinked with GParted Live CD
2. Shrinked partition(dev/hda5) so that unneeded space is left as unallocated
3. Created new hard disk with enough space and attached it to VM
4. Booted up with GParted Live CD and copied all partitions to new disk(except unallocated partitions)
5. Created new VM with new disk
6. After that, I booted up new VM with Rescue Live CD, and entered into grub:
6.1. grub>root (hd0,0)
6.2. grub>setup (hd0)
7. Reboot!
Now I have the same VM, just it's using over 50GB less space. :)
Thanks!
Edited by: DBagy on Jan 15, 2013 5:00 AM

Virtual Disk used Size is Zero

Hi All,
Got a 3.0.2 test environment, 2 hosts with a seperate physical VM Manager box. Been creating Xen PVM guests using both a downloaded OL5U7 template to clone from as well as using network boot to extracted iso via ftp (also OL5U7).
For the clones, I noticed the virtual disk name defaults to a 32-character string while I could name the virtual disk for the network boot method. What's the best practise for organising this? Should I leave the Virtual Disk name blank so it defaults to a 32-character string like the cloned guests?
Also, in Homes > Server Pools > Repositories > Virtual Disks, the cloned guests are showing the correct virtual disk usage but for the guests created using network boot to iso is showing zero for disk usage. The only difference I see between the 2 types of guests is the giest created using the extrated iso is using lvm for the root partition.
Is there a way to refresh the ovm manager view such that the disk usage is accurate for the guests?
Thanks.

831583 wrote:
For the clones, I noticed the virtual disk name defaults to a 32-character string while I could name the virtual disk for the network boot method. What's the best practise for organising this? Should I leave the Virtual Disk name blank so it defaults to a 32-character string like the cloned guests?Up to you. The actual filename will always be the UUID. The Manager just allows you to name new disks for display in the Manager only.
Also, in Homes > Server Pools > Repositories > Virtual Disks, the cloned guests are showing the correct virtual disk usage but for the guests created using network boot to iso is showing zero for disk usage. The only difference I see between the 2 types of guests is the giest created using the extrated iso is using lvm for the root partition.Correct. For a Network Boot image, the initial disk usage is 0. This will increase over time as more content is stored inside the image.
Is there a way to refresh the ovm manager view such that the disk usage is accurate for the guests?Refresh the repository.

Can Windows Server Backup spread a single backup job across multiple disks if they are not set up as a virtual disk?

This may be a dumb question, but I can't seem to find any definitive information after having done many, many searches. Short question is - can Windows Server Backup spread a single backup job across multiple disks if they are not in a storage
pool or some other RAID/JBOD structure?
Background:
I'm running Server 2012 Essentials with all Windows Updates installed. I have been backing up approx 2.8TB of data (Bare Metal Recovery, C:, S: (shared folders), and system reserved) for the past year+ onto a storage pool made up of two-2TB external
USB drives. Backup is slow (takes approx 1.5 days to complete), but generally works. Not surprisingly I was constantly getting capacity low messages so I decided to increase my backup storage pool by adding a 3TB drive and another spare 750GB drive
for a total of 7.75TB. Instead of having four separate external USB enclosures, I bot a 4-bay enclosure - Startech.com model #S3540BU33E to simplify this (or so I thought!).
The first problem I had was adding the two new drives to the existing storage pool. I think that is because the Startech uses a JMicron USB controller that reports identical uniqueid's for all drives so only one shows up in the GUI interface for creating storage
pools. After doing research on this, I set up a new storage pool and virtual disk using all four drives via Powershell and thought I was good. However, when the backup ran, it failed after filling the first drive, saying there was no remaining capacity. In
reality there were three remaining empty drives and there storage pool reported almost 5TB of avail capacity. I assumed this was due to the identical uniqueid issue so I decided to try a different tactic.
Instead of using a storage pool that combines all four disks into one virtual disk, I just added each of them to Windows Server Backup as individual drives thinking it would manage them collectively. I.e., when a drive filled up during a particular backup,
it would just start using the next drive and so on. Apparently this was a foolish assumption because the backup failed again as soon as the first disk filled up.
So now I don't know if this is still an issue with the identical uniqueid's or if Server Backup actually can't spread a single backup across multiple individual drives that aren't in a pool or other virtual disk implementation. Hence, my original question.
My guess is that it does *not* spread them across individual disks, but I just wanted to get confirmation.
Thanks

Mandy,
Thank you for following up on my question.
Unfortunately the article you referenced doesn't address what I am trying to accomplish.
The article focuses on saving the same backup job to multiple disks and rotating the disks between on and offsite for enhanced protection. However, it still requires that an individual backup job fits on a single disk.
What I am trying to determine is if a single backup job can span across more than one physical disk (during the backup process) without those physical disks being in some type of virtual disk implementation (e.g., storage pool, RAID, etc.).
Thanks,
Gerry

Unable to repair degraded Virtual disks in Storage Spaces under Hyper-V 2012 R2 Core

Hi all,
I am finding myself in the following conundrum. I have a storage pool under Hyper-V Core, with 2 2TB Seagate drives.
One of the drives completely died (wouldn't spin up, tried it in a different box, still to no avail). I sent it in to Seagate for warranty replacement, got the new drive. Installed it and went through the notions of adding it to the pool and retiring the
one that was with "Lost Communication" status.
Tried to repair the virtual disks that are showing as "Unhealthy-Detached", quickly get 100% complete, but the repair didnt work.
The storage pool is in degraded state.
Looks like metadata is corrupted.
Followed this post to upgrade Storage Spaces to latest version:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/eead59e9-5e49-4bb6-8cbb-1dafddd9576b/unable-to-repair-degraded-virtual-disks-in-storage-spaces-2012r2?forum=winserverfiles
Still, to no avail.
Couple of questions:
1) Is the data on the 3 virtual disks in state "Unhealthy: Detached" not recoverable?
2) How can I get the storage pool back to "healthy"?
Any help will be greatly appreciated.
PS C:\corefig> Get-PhysicalDisk | ? OperationalStatus -ne OK | fl
ObjectId : {1}\\HV001\root/Microsoft/Windows/Storage/Pr
oviders_v2\SPACES_PhysicalDisk.ObjectId="{95
42513c-a0d4-11e3-8123-806e6f6e6963}:PD:{7e22
245f-0cf6-11e3-b1db-806e6f6e6963}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId :
AllocatedSize : 1218696970240
BusType : Unknown
CannotPoolReason : In a Pool
CanPool : False
Description :
DeviceId :
EnclosureNumber :
FirmwareVersion :
FriendlyName : PhysicalDisk-1
HealthStatus : Warning
IsIndicationEnabled :
IsPartial : False
LogicalSectorSize : 0
Manufacturer :
MediaType : UnSpecified
Model :
OperationalStatus : Lost Communication
OtherCannotPoolReasonDescription :
PartNumber :
PhysicalLocation :
PhysicalSectorSize : 0
SerialNumber :
Size : 1999575711744
SlotNumber :
SoftwareVersion :
SpindleSpeed : 0
SupportedUsages : {Auto-Select, Manual-Select, Hot Spare,
Retired...}
Usage : Retired
PSComputerName :
PS C:\corefig> get-physicaldisk
FriendlyName CanPool OperationalS HealthStatus Usage Size
tatus
PhysicalDisk4 False OK Healthy Auto-Select 73.75 GB
PhysicalDisk0 False OK Healthy Auto-Select 1.82 TB
PhysicalDi... False Lost Comm... Warning Retired 1.82 TB
PhysicalDisk2 False OK Healthy Auto-Select 930.75 GB
PhysicalDisk3 False OK Healthy Auto-Select 74.53 GB
PhysicalDisk1 False OK Healthy Auto-Select 1.82 TB
PS C:\corefig> get-virtualdisk -friendlyname 'Data' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2229cf-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = CF29227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 548413636608
DetachedReason = Incomplete
FootprintOnPool = 1096827273216
FriendlyName = Data
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1099511627776
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Backups' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e22255e-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = 5E25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 743566213120
DetachedReason = Incomplete
FootprintOnPool = 1487132426240
FriendlyName = Backups
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1649267441664
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Music' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2238b9-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = B938227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 39728447488
DetachedReason = By Policy
FootprintOnPool = 79456894976
FriendlyName = Music
HealthStatus = Unknown
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = True
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 161061273600
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Videos' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2225bc-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = BC25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 223606734848
DetachedReason = Incomplete
FootprintOnPool = 447213469696
FriendlyName = Videos
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1759325978624
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =

Hi omon_77,
You can first refer the following step by step third party article and KB:
Replace Failed Disks and Repair JBODs for Storage Spaces in Windows Server
https://technet.microsoft.com/en-us/library/dn782852.aspx?f=255&MSPPError=-2147217396
Replacing a failed disk in Windows Server 2012 Storage Spaces with PowerShell
https://www.hodgkins.net.au/storage/replace-failed-disk-in-storage-spaces-pool-with-powershell/
Step By Step: How to Replace Faulty Disk In Two-Way Mirrored Storage Tiered Space
http://charbelnemnom.com/2014/09/step-by-step-how-to-replace-faulty-disk-in-two-way-mirrored-storage-tiered-space-storagespaces-ws2012r2/
More information:
Storage Spaces - Designing for Performance
http://social.technet.microsoft.com/wiki/contents/articles/15200.storage-spaces-designing-for-performance.aspx
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
Windows Server Storage Spaces: What is it and why should I use it?
http://curah.microsoft.com/5049/windows-server-2012-r2-storage-spaces-what-is-it-and-why-should-i-use-it
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Storage Spaces: Virtual Disk taken offline during file copy, marked as "This disk is offline because it is out of capacity", but plenty of free space

Server 2012 RC. I'm using Storage Spaces, with two virtual disks across 23 underlying physical disks.
* First virtual disk is fixed provisioning, parity across 23 physical disks: 10,024GB capacity
* Second virtual disk is fixed provisioning, parity across the remaining space on 6 of the same physical disks: 652GB capacity
These have been configured as dynamic disks, with an NTFS volume spanned across the two (larger virtual disk first). Total volume size 10,676GB. For more details of the hardware, and why the configuration is like this, see: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/c35ff156-01a8-456a-9190-04c7bcfc048e
I'm copying several TB from a network share to this volume. It is very slow at ~12MB/sec, but works. However, three times so far, several hours in to the file copy and with plenty of free space remaining, the 10,024GB virtual disk is suddenly taken offline.
This obviously then fails the spanned volume and stops the file copy.
The second time, I took screenshots, below. The disk (Disk27) is marked offline due to "This disk is offline because it is out of capacity". And the disk in the spanned volume is marked as missing (which is what you would expect when one of its member disks
is offline).
I can then mark the disk (Disk27) back online again, and this restores the spanned volume. I can then re-start the file copy from where it failed. There doesn't appear to be any data loss, but it does cause an outage that requires manual attention. As you
can see, there is plenty of space left on the spanned volume.
Each time this has happened, there are a few event 150 errors in the System event log: "Disk 27 has reached a logical block provisioning permanent resource exhaustion condition.". Source: Disk.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="disk" />
<EventID Qualifiers="49156">150</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-06-07T11:24:53.572101500Z" />
<EventRecordID>14476</EventRecordID>
<Channel>System</Channel>
<Computer>Trounce-Server2.trounce.corp</Computer>
<Security />
</System>
- <EventData>
<Data>\Device\Harddisk27\DR27</Data>
<Data>27</Data>
<Binary>000000000200300000000000960004C0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
This error seems to be related to thin provisioning of disks. I found this:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848068(v=vs.85).aspx. But both these Virtual Disks are configured as Fixed, not Thin provisioning, so it shouldn't apply.
My thoughts: the virtual disk should not spuriously go offline during a file copy, even if it was out of space. And in any case, there is plenty of free space remaining. Also, I don't understand the reason for why it is marked as offline ("This disk is offline
because it is out of capacity"). Why would a disk go offline because it was out of thin capacity, rather than just returning an "out of disk space" error while keeping it online.

Interesting Thread, I've been having the same issue. I had a failed hardware RAID that was impossible to recover in place, so after being forced to do a 1:1 backup, I find myself with 5 2TB hard drives to play with. Storage Spaces seemed like an interesting
way to go until I started facing the issues we share.
So my configuration is A VM Running Windows Server 2012 RC with 5 Virtualized Physical drives using a SCSI interface, 2TB in size that make up my storage pool. A Single Thinly provisioned Disk of 18 TB (using 1 disk for parity)
Interestly enough, write speed has not been an issue on this machine (30~70MB/s, up from 256k on the beta)
Of note to me is this error in my event log 13 minutes before the drive disappeared:
"The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time.Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."Source: volsnap, Event ID: 25, Level: Error
followed by:
"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume17.(The physical resources of this disk have been exhausted.)"Source: Ntfs (Microsoft-Windows-Ntfs), Event ID: 140, Level: Warning
I figure the amount of space available to me before I start encountering physical limits is in the vicinity of about 7TB. It dropped out for the second time at 184 GB.
FYI, the number of columns created for me is 5
Regards,
Steven Blom

Windows 2003 Guest cannot access "SCSI" virtual Disks with /PAE enabled

I created a Windows 2003 EE R2 guest with 16 GB memeory, 48 GB System disk and 4 virtual SCSI disks for Microsoft Cluster services. It all worked, but limited Windows to 3.75 GB memory. When I added the /PAE option to boot.ini, the memory was available, but the virtual SCSI disks were unavailable. Has any else seen this behavior? Is there a work-around? since I need 4 additional virtual disks for the cluster, I cannot make them all IDE drives.

/OVS is on local storage and /OVS/sharedDisks is an OCFS2 formatted logical volume mounted from a Fiber Channel SAN.
--- Logical volume ---
LV Name /dev/vievg/vie_data
VG Name vievg
LV UUID LQJc0N-HkIn-46gQ-RdXc-0eSn-iRVn-VckVbj
LV Write Access read/write
LV Status available
# open 2
LV Size 383.99 GB
Current LE 98301
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:0
LABEL=/ / ext3 defaults 1 1
/dev/cciss/c0d1p1 /OVS ocfs2 defaults 1 0
LABEL=/boot1 /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=SW-cciss/c0d0p3 swap swap defaults 0 0
/dev/vievg/vie_data /OVS/sharedDisk ocfs2 defaults 1 0
acpi = 1
apic = 1
boot = 'd'
builder = 'hvm'
device_model = '/usr/lib/xen/bin/qemu-dm'
disk = ['file:/OVS/running_pool/77_VHAISPMUL13A/System.img,hda,w',
'file:/OVS/sharedDisk/VHAISPCLU13_L.img,sdb,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_P.img,sdc,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_S.img,sdd,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_Q.img,sda,w!',
'file:/OVS/iso_pool/Windows_2003/en_win_srv_2003_r2_enterprise_with_sp2_vl_cd1_X13-48610.iso,hdc:cdrom,r',
disk_other_config = []
kernel = '/usr/lib/xen/boot/hvmloader'
keymap = 'en-us'
maxmem = 16384
memory = 16384
name = '77_VHAISPMUL13A'
on_crash = 'restart'
on_reboot = 'restart'
pae = 1
serial = 'pty'
timer_mode = 1
usbdevice = 'tablet'
uuid = 'ddab0147-6dde-4a2e-2c00-b883a16058ac'
vcpus = 2
vif = ['bridge=xenbr0,mac=00:16:3E:19:C1:E9,type=ioemu',
'bridge=xenbr1,mac=00:16:3E:55:17:AC,type=ioemu',
vif_other_config = []
vnc = 1
vncconsole = 1
vnclisten = '0.0.0.0'
vncpasswd = 'passw0rd'
vncunused = 1
It works fine without the /PAE flag, so I am wondering if it is an issue with the Windows driver for the sd devices presented by the virtual machine emulator and if there is a way to select a better driver.

IPod nano - Incorrect Available Size

My nano always report 1.8GB "Available" size no matter there is no or full with songs. iTunes can report the correct available space.
I have reset the nano, press the menu and select button, which didn't help.
Anyone meet similar problem? Can anyone help? Please and thanks in advance.

It's not missing anything.
Is It Missing Space?
iPod: About Hard Disk Size
bd

Relocating virtual disks to file systems other than dom0:/OVS/running_pool

It looks like the best approach for having multiple large file systems mounted within a domU is by:
1.) Use VM Mgr to create dummy virtual disk (within dom0:/OVS/running_pool/domU)
2.a) if size of dummy is large enough, cp it to a different file system within domU
2.b) if size of dummy is too small, create a new file on different file system within domU using dd
3.) Replace dummy virtual disk file (within dom0:/OVS...) with symbolic link that reference the new replacement file.
Are others doing this? Is there a better way?
Does it cause problems?
is there a way to update VM Mgr to show the correct size if the virt disk is enlarged from the size of the original dummy virtual disk?
Thx...
Edited by: twtuck on Mar 9, 2009 8:29 AM

You can use the /usr/lib/ovs/ovs-makerepo script to add additional repositories under the /OVS mount point. The script takes a block device as a parameter. For example, to create a new shared location on /dev/mapper/mpath1p1, you would run:
# /usr/lib/ovs/ovs-makerepo /dev/mapper/mpath1p1 1 "Shared Storage"
These repositories are then visible to Oracle VM and VM Manager. It will use the repository with the most amount of available space to create your guests for you.

Virtual Disk mis-reporting available size

Similar Messages

Maybe you are looking for