Unsolved
This post is more than 5 years old
22 Posts
0
1232
File system expansion error
Hi All,
I was trying to expand the file system on the source NAS box. But receiving an error.
[nasadmin@Alinta_Tal_NAS server]$ nas_fs -xtend pfs_vtalpwfile01 size=116GB pool=clarata_archive
Error 5008: Remote command failed:
remote celerra = Alinta_Bur_NAS
remote exit status = 5
remote error = 0
remote message = CLATA : volume(s) are not available
I think its probably trying to extend the Destination file system and there is no space there . Could any one throw a light on this issue as we have a delay in creating a share drive on the file system which we are trying to expand. This file system is built of ATA drives.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 20th, 2011 19:00
yes, if file system is setup for replication when you expand source ..it will automatically try to expand target.
maddykrish
22 Posts
0
April 20th, 2011 20:00
Hi Dynamox
Thanks for that.
But i am receving an error while expanding the file system ..Could you please say what can be done to avoid this error ?
[nasadmin@Alinta_Tal_NAS server]$ nas_fs -xtend pfs_vtalpwfile01 size=116GB pool=clarata_archive
Error 5008: Remote command failed:
remote celerra = Alinta_Bur_NAS
remote exit status = 5
remote error = 0
remote message = CLATA : volume(s) are not available
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 20th, 2011 21:00
can you post output from this command for source and target:
nas_pool -size clarata_archive
maddykrish
22 Posts
0
April 20th, 2011 21:00
Hi Dynamox
The target celerra pool clarata_archive is having a good space. But still getting an error. Tried to manually extend DR file system on the DR nas no luck.
Please advice.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 20th, 2011 21:00
look at the pool on the target Celerra ..if it does not have enought storage you need to add some otherwise how can you replicate file system where source is bigger than target ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 20th, 2011 22:00
interesting, target has plenty of space. Can you run "nas_log server_2" on DR and look for any error messages around the time you tried to extend the file system on source Celerra.
maddykrish
22 Posts
0
April 20th, 2011 22:00
Source NAS
id = 10
name = clarata_archive
used_mb = 13556488
avail_mb = 523502
total_mb = 14079990
potential_mb = 327679
DR NAS
id = 10
name = clarata_archive
used_mb = 12289614
avail_mb = 1790376
total_mb = 14079990
potential_mb = 0
maddykrish
22 Posts
0
May 8th, 2011 23:00
Hi Thanks..
The condition here is that the DR Clariion hooked to the DR NAS is not having space.
As per my understanding the file system is trying to span across multiple backends hooked on to the DR NAS.
The space is more on the DR NAS CLARATA_ARCHIVE pool but the file system is out of one backend and that backend is having less space.
id = 10
name = clarata_archive
used_mb = 12289614
avail_mb = 1790376 <<<<<<<<<<<
total_mb = 14079990
potential_mb = 0
you told about slice = y . .Are you asking me to extend the source file system by giving option slice= y..
Can you explain this please ?
Currently we are seeing how to replace the exisiting SATA drives with higher TB SATA drives.
Regards
Krishna Prasad.S
christopher_ime
2K Posts
0
May 8th, 2011 23:00
Based on the error message and seeing the available space that actually exists, this suggests that it is trying to assign a full dvol (underlying lun) instead of "slicing" from the underlying components. Try running the command with: "-option slice=y". If this works then it suggests that the setting for the storage pool itself is slice=n.
btw, this is not the default for the standard CLARiiON AVM storage pools which (by name at least) clarata_archive belongs to, but this could have been changed in the storage pool properties (un)intentionally. You can view/modify the storage pool properties from either the GUI or using the appropriate nas_pool command.