DBCC CheckDB runs out of disk space for sparse file. Is it possisble to redirect sparse file to other volumes?

Hi experts,

  We got an error: Error Text of the Database: "Write to sparse file
  'I:\tcpdata1\TCPDATA4.ndf:MSSQL_DBCC7' failed due to lack of disk space."

Q1: Does this mean I should always left maybe 10% ~ 20 % disk space for checkdb on each volume where database files located?

Q2: Is it possible to redirect sparse file to other volumes?

Q3: How to solve this problem more gracefully?

Q4: I have a database size: 9.8TB and it took more than two days to run dbcc checkdb with physical_only with max degree of parallemlism = 1. Does this make sense?

---- errorlog ----

2015-04-21 13:21:58.08 spid239     Error: 17053, Severity: 16, State: 1.
2015-04-21 13:21:58.08 spid239     I:\tcpdata1\TCPDATA4.ndf:MSSQL_DBCC7: Operating system error 112(There is not enough space on the disk.) encountered.
2015-04-21 13:21:58.09 spid239     Error: 17053, Severity: 16, State: 1.
2015-04-21 13:21:58.09 spid239     I:\tcpdata1\TCPDATA4.ndf:MSSQL_DBCC7: Operating system error 112(There is not enough space on the disk.) encountered.
2015-04-21 13:21:58.10 spid239     Error: 17053, Severity: 16, State: 1.
2015-04-21 13:21:58.10 spid239     I:\tcpdata1\TCPDATA4.ndf:MSSQL_DBCC7: Operating system error 112(There is not enough space on the disk.) encountered.
2015-04-21 13:21:58.10 spid239     Error: 17053, Severity: 16, State: 1.
2015-04-21 13:21:58.10 spid239     I:\tcpdata1\TCPDATA4.ndf:MSSQL_DBCC7: Operating system error 112(There is not enough space on the disk.) encountered.
2015-04-21 13:21:58.38 spid1895    Error: 17053, Severity: 16, State: 1.

Log  Job History (SAP CCMS Check Database TCP [20140606154429-7-010000])Step ID  1
Server  DL980-3
Job Name  SAP CCMS Check Database TCP [20140606154429-7-010000]
Step Name  CCMS-Step1
Duration  2.12:26:13
Sql Severity 16
Sql Message ID 16389
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0Message
Executed as user: tcp. ...r indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282329), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282330), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282331), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282332), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282333), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282334), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282335), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282944), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282945), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282946), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282947), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282948), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282949), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282950), whose header indicates that it is allocated to object ID 1950486573, index ID 1, partition ID 72057625115164672, alloc unit ID 72057625355419648 (type In-row data), is allocated by another object. [SQLSTATE 42000] (Error 2534)  Table error: page (3:13282951), whose header indicates that it is allocated to object ID 19504...  The step failed.