Start a Conversation

Unsolved

This post is more than 5 years old

1024

June 14th, 2012 22:00

ISCSI Replication fail

Regarding a disk space problem on our 900gb filesystem used for our primary Microsoft Exchange databases hosted on 2 x 250GB iscsi luns on this filesystem. The iscsi luns are also replicated to our DR Celerra. Since creating the 2 new 250gb iscsi luns(16,17), deleting the old replication and 2 x 200gb iscsi luns (9,11) and setting up replication for the new luns we have no disk space left on the 900gb filesystem.

Previously the filesystem was 500gb (when hosting the 2 x 200gb luns 9 and 11) with replication and had spare space so we struggle to understand why an extended 900gb filesystem hosting 2 x 250gb iscsi luns is full!.

Replication has now stopped due to the filesystem being full - it was working for a few days prior to this.

I'm getting error message when he start the replication

"

Slot 2: Source Scheduler=fs71_T1_LUN16_SL7E9101800001_0000_fs25_T1_LUN16_SL7E9101800030_0000(alias=ExchangeDB1_Rep), refreshing an internal checkpoint failed:DpRequest_vs_OutOfSpace. Session inactive.

1 Rookie

 • 

65 Posts

June 20th, 2012 05:00

HI Sameer,

Thanks,

My file system size is already 900 GB

Please let me know, what's is allocation size.alloc=311MB, alloc=216286MB.

Can i freeup by deleting ISCSI snapshot for lun17.

(Production) fsid=71 size=256000MB alloc=311MB dense path=/ExchangeDB/fs71_T1_LUN16_SL7E9101800001_0000/fs71_T1_LUN16_SL7E9101800001_0000 (snapped)

(Production) fsid=71 size=256000MB alloc=216286MB dense path=/ExchangeDB/fs71_T1_LUN17_SL7E9101800001_0000/fs71_T1_LUN17_SL7E9101800001_0000

Connected Initiators:

296 Posts

June 20th, 2012 05:00

Hi,

you may have to extend the file system size on which iSCSI lun exists as the snapshots for iSCSI lun will be saved in the file system.

Sameer Kulkarni

No Events found!

Top