I've seen something similar with very large GPT fileserver volumes. It's as if the equivalent to VTOC doesn't get properly updated.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Tuesday, September 16, 2014 6:07 PM To: [email protected] Subject: RE: [NTSysADM] OT: DPM <wipes nervous sweat from brow> Hour glass finally went away and put the disk back online. Did a rescan disks and then created the backup job. Success. I'm glad I found that article; still not 100% sure what went wonky but it looks like it's unwonked now. ---------------------------------------- > From: [email protected] > To: [email protected] > Subject: [NTSysADM] OT: DPM > Date: Tue, 16 Sep 2014 14:32:04 -0700 > > Originally didn't want to post this here as I prefer to stay on-topic... > > DPM 2012 SP1 > I've a job running (for Exchange) to backup a database and of course truncate > the logs. It keeps failing with: > DPM is out of disk space for the replica. (ID 58 Details: There is not > enough space on the disk (0x80070070)) > > I've already gone on the SAN and expanded the volume by 4TB (making it 20TB > total) and this extra, unallocated space shows in Disk Management on the > server. In Modify Disk Allocation the Data Size shows as 317.2GB (though it's > 171GB on disk), Replica Volume fills in as 280GB and Recovery Point Volume > fills in as 60GB. Automatically Grow the Volumes is checked and don't have a > problem with other jobs. I'm at a bit of a loss as to how fix this. > NB1: if I increase the Replica Volume size beyond 300GB it fails with: > Modifying disk allocation for DU007 failed: > Error 360: The operation failed due to a virtual disk service error > Error details: VdsError:The specified disk extent size exceeds the size of > free disk space. > (0x80042515) > Recommended action: Retry the operation. > > Yet it does not exceed the size; as I mentioned there are 4TB available. > > NB2: I found one posting on MS' site with the exact same message. Someone > replied to put the volume offline, then online and rescan disks. The original > poster said that worked. So I set it to offline (no jobs currently running); > that was almost an hour ago and still have the hour glass. > >
