Hi Rainer,  yes I did. Found 3 articles:  1. to delete the replication, extend then re-create (this one: [URL]  2. was a post on the community where someone had the same issue I did but between 2 VNXe's not like I have. There was a reply from an engineer that stated 2 options regarding the VNXe software to proceed. First if the VNXe software was pre-mr4 to do the delete replication operations, 2nd if it was after mr4 to just pause the replication and then extend the FS on both arrays. Thing is, the solution was for 2 VNXe's. Found it here: [URL]  3. Another solution I found and answer was if the source gets expanded the target will too if it has enough space. Problem in my case is that the source is the VNXe and the size of the FS is greyed out and I cannot expand it.  My concern is the read-only VDM on the target VNX, because from how I see it even if I delete the replication I can extend only source as target is still mounted on the read-only VDM so I cant expand it. Question is, if I unmount it, will I loose settings and exports that are already configured? It has some shares, snapshots etc.  Also, beside all the above, should I consider something else before proceeding?  Many thanks [IMAGE]   LATER EDIT:  I did pause the replication, gave few errors but it got paused. Expanded source FS, went on VNX5800 and modified the VDM to R/W and expanded the target FS, then modified back on proprieties read-only. Went back to source FS on VNXe and tried to resume replication - it failed. Deleted replication successfuly but now when I want to re-create the replication from the VNXe I can only see the target VNX but the storage resource (the FS on target VNX) cant be found... Any thoughts?  LATER LATER EDIT:  Apparently the storage resource on the target couldnt be found because as the target filesystem was checked as Thin, the capacity was indeed increased to what I needed but on the properties of the filesystem the "Maximum capacity (MB)" didnt change along with the capacity increase. I had to again switch the FS on the mount to R/W, modify that filed with the new value, switch back to R/O. After this operations the VNXe could see both the target VNX and the filesystem.  Lesson learned.
Hello,  I have some doubts about a normal extension of a file system but in a replicated environment.  Scenario is: VNXe as source and VNX 5800 as target.  I read that in order to expand the file system I have to delete the replication session, extend FS on both arrays and then re-create the replication session.  Thing is, I dont know what I can break [IMAGE]. The consequences. When I tried at first to extend the destination file system (until I figured it out it was replicated) it said that the FS is mounted on a read-only datamover. That being said, now I have to delete the replication, expand the source FS, unmount the FS from the read-only datamover (will that cause any issues?), expand the FS on the target VNX then mount again and re-create the replication.  I tried to consider as many points as possible in order not to break something, is there anything missing that I have to look into before doing this?  Thanks a lot, Adel
VNXe and VNX file system extension with replication