You only need to have space available to extend the filesystem in the same type of disk configuration - the extend operation is online and quick - no effect on any data or user access.
However, it is recommended that, you don't mix up the storage pools in the process of extension - i.e. try NOT to extend a file system using clar_r5_economy pool where the file system was originally created on clar_r5_performance pool.
You can not mix the file systems of different disk type - i.e. can not extend a file system created on FC disks to SATA disks. The extend option will show you only available storage pools.
Extending the filesystem should be pretty straightforward. If this is your first time, you might want to perform the steps in the the web GUI. Login to the web interface for your control station and select Filesystems from the left-hand menu:
Simply select the filesystem you want to extend, right click on it, and select Extend from the menu. You'll see a new window where you can select the storage pool you want to use, how much space to add (in Megabytes) and so on.
You'll see how much space is available in the field that says Extend With Storage Pool. If you have more than one storage pool configured, you should use the same pool to extend your filesystem (you'll see which pool is in use in the Current Storage Pools field). In my case, I'm extending a 10GB filesystem that's on pool clar_r5_economy, with more space from the same pool.
You can also do this from the command line, but this is often the easiest way when you're unfamiliar with the steps.
This post was really helpful but my issue is that the filesystem is being replicated to another location. Can anyone tell me how I extend a file system in this case?
same process, when you extend source file system, replica file system gets extended automatically. Just make sure you have enough space on the target Celerra/VNX.
No - the replication can continue. The source Celerra communicates with the target Celerra over the Celerra interconnect, and the source tells the target to extend it's filesystem. It's quite easy, if you have the space...
nandas
4 Operator
•
1.5K Posts
0
April 13th, 2010 14:00
You only need to have space available to extend the filesystem in the same type of disk configuration - the extend operation is online and quick - no effect on any data or user access.
However, it is recommended that, you don't mix up the storage pools in the process of extension - i.e. try NOT to extend a file system using clar_r5_economy pool where the file system was originally created on clar_r5_performance pool.
You can not mix the file systems of different disk type - i.e. can not extend a file system created on FC disks to SATA disks. The extend option will show you only available storage pools.
My 2 cents
Thanks,
Sandip
umichklewis_ac7b91
300 Posts
0
April 12th, 2010 16:00
Hi!
Extending the filesystem should be pretty straightforward. If this is your first time, you might want to perform the steps in the the web GUI. Login to the web interface for your control station and select Filesystems from the left-hand menu:
Simply select the filesystem you want to extend, right click on it, and select Extend from the menu. You'll see a new window where you can select the storage pool you want to use, how much space to add (in Megabytes) and so on.
You'll see how much space is available in the field that says Extend With Storage Pool. If you have more than one storage pool configured, you should use the same pool to extend your filesystem (you'll see which pool is in use in the Current Storage Pools field). In my case, I'm extending a 10GB filesystem that's on pool clar_r5_economy, with more space from the same pool.
You can also do this from the command line, but this is often the easiest way when you're unfamiliar with the steps.
Let us know if this works for you!
Karl
umichklewis_ac7b91
300 Posts
0
April 13th, 2010 14:00
Ah yes, indeed! (Says the man who misplaced a zero and extended a 60GB share to 6TB; I had to delete it and recreate it!)
Rainer_EMC
4 Operator
•
8.6K Posts
0
April 13th, 2010 14:00
as Karl nicely showed its really easy as long as you have space available in the pool
nothing to check - no umount or downtime required - completely online
it just takes a couple of seconds at most and your Solaris server will then immediately see more free space
just read carefully that the extension size is specified in MegaBytes (not GB)
Rainer
dynamox
9 Legend
•
20.4K Posts
0
April 13th, 2010 14:00
I did that on a production file system, had to migrate customer to another (smaller) file system
bharatdara23
11 Posts
0
May 14th, 2014 12:00
This post was really helpful but my issue is that the filesystem is being replicated to another location. Can anyone tell me how I extend a file system in this case?
dynamox
9 Legend
•
20.4K Posts
0
May 14th, 2014 12:00
have you since added more space to destination array ?
Exterminator1
4 Posts
0
May 14th, 2014 12:00
Curious to know what we can do in this situation.
bharatdara23
11 Posts
0
May 14th, 2014 12:00
Yes, I did add space to the destination array.
dynamox
9 Legend
•
20.4K Posts
1
May 14th, 2014 12:00
same process, when you extend source file system, replica file system gets extended automatically. Just make sure you have enough space on the target Celerra/VNX.
bharatdara23
11 Posts
0
May 14th, 2014 12:00
I increased the source side without the space on the destination side. It now doesn't allow me to do anything.
Exterminator1
4 Posts
0
May 14th, 2014 13:00
Doesn't he have to stop the replication to do that?
dynamox
9 Legend
•
20.4K Posts
0
May 14th, 2014 13:00
try to increase source file system, but 1g or something of that nature.
umichklewis
3 Apprentice
•
1.2K Posts
0
May 14th, 2014 14:00
No - the replication can continue. The source Celerra communicates with the target Celerra over the Celerra interconnect, and the source tells the target to extend it's filesystem. It's quite easy, if you have the space...
bharatdara23
11 Posts
0
May 15th, 2014 07:00
Does anyone have any documents where I can learn more about the extending the Celerra file system, Celerra interconnects and all?