Unsolved
This post is more than 5 years old
1 Rookie
•
14 Posts
0
1690
April 15th, 2009 06:00
Replication V2 version out of space
Hello all,
I'm experiencing some errors creating a replication session from a NS20 regarding iSCSI LUN to a destination with readonly iSCSI LUN same size.
Starting from my wizard I'm able to determine my readonly LUN on my destination but when finishing the process a warning message pop up - "version set out of space".
The proper recommendation is to extend my file system or my iSCSI LUN.
This is cause my file system which these LUNS are created is totally full.
These file system were not created with virtual provisioning and this would help solve this problem or even it does not happen.
I have about 146GB in a RAID GROUP+146GB in another one and a last one with 73GB. I really could deliver those to Celerra but I think this could help like a workaround and not a definitive solution.
Also troubleshooting saw my SavVol is full like said previously and would like to measure a specific growth rate, beign that my storage is almost full capacity.
Follow my specific environment outputs and if anyone has an idea please let me know.
[nasadmin@csdumas ~]$ nas_fs -i fs07
Thanks a lot friends.
I'm experiencing some errors creating a replication session from a NS20 regarding iSCSI LUN to a destination with readonly iSCSI LUN same size.
Starting from my wizard I'm able to determine my readonly LUN on my destination but when finishing the process a warning message pop up - "version set out of space".
The proper recommendation is to extend my file system or my iSCSI LUN.
This is cause my file system which these LUNS are created is totally full.
These file system were not created with virtual provisioning and this would help solve this problem or even it does not happen.
I have about 146GB in a RAID GROUP+146GB in another one and a last one with 73GB. I really could deliver those to Celerra but I think this could help like a workaround and not a definitive solution.
Also troubleshooting saw my SavVol is full like said previously and would like to measure a specific growth rate, beign that my storage is almost full capacity.
Follow my specific environment outputs and if anyone has an idea please let me know.
[nasadmin@csdumas ~]$ nas_fs -i fs07
id = 31
name = fs07
acl = 0
in_use = True
type = uxfs
worm = off
volume = v126
pool = vmware_pool_01
member_of = root_avm_fs_group_40
rw_servers= server_2
ro_servers=
rw_vdms =
ro_vdms =
auto_ext = no,virtual_provision=no
stor_devs = CK200084700666-001C,CK200084700666-0013
disks = d19,d20
disk=d19 stor_dev=CK200084700666-001C addr=c0t2l0 server=server_2
disk=d19 stor_dev=CK200084700666-001C addr=c16t2l0 server=server_2
disk=d20 stor_dev=CK200084700666-0013 addr=c16t1l9 server=server_2
disk=d20 stor_dev=CK200084700666-0013 addr=c0t1l9 server=server_2
[nasadmin@csdumas ~]$ nas_volume -s v126 total = 512000 avail = 0 used
= 512000 ( 100% ) (sizes in MB)
[nasadmin@csdumas ~]$ server_df server_2
server_2 :
Filesystem kbytes used avail capacity Mounted on
FS_REPLICACAO_250GB_1
268469744 261248200 7221544 97% /FS_REPLICACAO_250GB_1 Storage_SATA-SAO_300Gb_01
309772784 308375240 1397544 100% /Storage_SATA-SAO_300Gb_01 FS01_FILESERVER_FC
2040977632 1758527032 282450600 86% /FS01_FILESERVER_FC FS04_VMWARE_HOMOLOG_SATA
258143984 257150224 993760 100% /FS02_VMWARE_HOMOLOG_SATA FS03_VMWARE_HOMOLOG_SATA
516287984 515324288 963696 100% /FS_VMWARE_HOMOLOG_SATA FS02_FILESERVER_SATA
516287984 2720 516285264 0% /fs01SATA
fs16 144558576 144557648 928 100% /fs16
fs15 444007664 443609272 398392 100% /fs15
fs14 278795504 278664728 130776 100% /fs14
fs13 72280304 72227936 52368 100% /fs13
fs12 92931824 92922832 8992 100% /fs12
fs10 516283888 512250784 4033104 99% /fs10
fs09 516287984 512250784 4037200 99% /fs09
fs08 516287984 512250784 4037200 99% /fs08
fs07 516287984 512250784 4037200 99% /fs07
root_fs_common 15368 5280 10088 34% /.etc_common
root_fs_2 258128 9648 248480 4% /
name = fs07
acl = 0
in_use = True
type = uxfs
worm = off
volume = v126
pool = vmware_pool_01
member_of = root_avm_fs_group_40
rw_servers= server_2
ro_servers=
rw_vdms =
ro_vdms =
auto_ext = no,virtual_provision=no
stor_devs = CK200084700666-001C,CK200084700666-0013
disks = d19,d20
disk=d19 stor_dev=CK200084700666-001C addr=c0t2l0 server=server_2
disk=d19 stor_dev=CK200084700666-001C addr=c16t2l0 server=server_2
disk=d20 stor_dev=CK200084700666-0013 addr=c16t1l9 server=server_2
disk=d20 stor_dev=CK200084700666-0013 addr=c0t1l9 server=server_2
[nasadmin@csdumas ~]$ nas_volume -s v126 total = 512000 avail = 0 used
= 512000 ( 100% ) (sizes in MB)
[nasadmin@csdumas ~]$ server_df server_2
server_2 :
Filesystem kbytes used avail capacity Mounted on
FS_REPLICACAO_250GB_1
268469744 261248200 7221544 97% /FS_REPLICACAO_250GB_1 Storage_SATA-SAO_300Gb_01
309772784 308375240 1397544 100% /Storage_SATA-SAO_300Gb_01 FS01_FILESERVER_FC
2040977632 1758527032 282450600 86% /FS01_FILESERVER_FC FS04_VMWARE_HOMOLOG_SATA
258143984 257150224 993760 100% /FS02_VMWARE_HOMOLOG_SATA FS03_VMWARE_HOMOLOG_SATA
516287984 515324288 963696 100% /FS_VMWARE_HOMOLOG_SATA FS02_FILESERVER_SATA
516287984 2720 516285264 0% /fs01SATA
fs16 144558576 144557648 928 100% /fs16
fs15 444007664 443609272 398392 100% /fs15
fs14 278795504 278664728 130776 100% /fs14
fs13 72280304 72227936 52368 100% /fs13
fs12 92931824 92922832 8992 100% /fs12
fs10 516283888 512250784 4033104 99% /fs10
fs09 516287984 512250784 4037200 99% /fs09
fs08 516287984 512250784 4037200 99% /fs08
fs07 516287984 512250784 4037200 99% /fs07
root_fs_common 15368 5280 10088 34% /.etc_common
root_fs_2 258128 9648 248480 4% /
Thanks a lot friends.
0 events found
No Events found!
Rainer_EMC
6 Operator
•
8.6K Posts
0
April 15th, 2009 14:00
for ISCSI snaps and replication the SAVVOL is not used - the snapshots are kept inside the same file system as the LUN
so you have two choices:
- extend the file system to allow for space for the snapshots
how much you can determine by looking at "Space required for next snapshot" in the LUN properties in the GUI or by calculating from the sizing Technote on Powerlink
both the source and the destination file system need enough space for snapshots in order for the replication to work
- delete the destination LUN and re-create it as virtually provisioned - then it *and* its snapshots wont require full space reservation.
in order to create a replication session to a VP LUN you currently need to use the CLI though - the GUI wont allow you to select it
creating the file system itself virtually provisioned or with auto-extension is (I believe) only supported if it contains VP LUNs but not for dense LUNs
regards
Rainer
vitera-kaizen
1 Rookie
•
14 Posts
0
April 16th, 2009 06:00
Thanks for response.
But I have a problem cause my file systems are complete full and already in use against my LUNS.
I tryed to enable auto-extend them but pop up an error cause they are already in use.
Error 2216: fs-07 : item is currently in use by iscsi
Also tryed to extend the volume that compose it.
Error 2216: v126 : item is currently in use by fs-07
Is there some other way to enable auto-extend or to xtend those file systems since they're in full production?
Thanks a lot friend!
Regards...
Rainer_EMC
6 Operator
•
8.6K Posts
0
April 17th, 2009 03:00
you just need to extend the file system manually (not the volume)
Either through the GUI on the File Systems page
or from the CLI nas_fs -xtend size= pool=
like nas_fs -xtend fs07 size=10G
vitera-kaizen
1 Rookie
•
14 Posts
0
April 17th, 2009 09:00
The procedure goes in a way almost creating a "clone" to the 1st snapshot and this snapshot in truth is replicated and later on just updating the common base for instance the 2nd snapshot in both sides.
I really appreciate your comments and really got the schema.
See ya!
Rainer_EMC
6 Operator
•
8.6K Posts
0
April 17th, 2009 10:00
they wont reserve any space up-front for either LUNs or snapshots
Just make sure that you combine it with good monitoring and/or automatic file system extension so that you catch it before the file system fills up