This post is more than 5 years old
53 Posts
0
3843
July 1st, 2010 06:00
Not enough Space in CIFS Share, the first time, then it's fine
I've had a dig around for a solution but haven't managed to really find anything on Powerlink on this !
I'm getting an error when copying files to a share on a CIFS server.
The CIFs server is defined on a VDM.
I've mapped a drive to a Windows XP SP3 PC, from the Celerra NS120 (Dart 6.4.8.701)
For the CIFs Share, I created a file system using the clar_r5_performance pool.
For the File System(FS) I selected the following options:
Storage capacity : 20MB
Auto Extend enabled: Yes
Virtual Provisioning Enabled:
High Watermark: 90
Maximum Capacity:40MB (required when virtual provisioning is enabled)
Slice Volumes: Yes
File retention : No
Deduplication Enabled: Yes
So from the XP machine, the mapped folder shows there is about 38MB of free space within the share - I set 40MB as the max capacity - so that's fine.
I copy 15MB of files and it's all fine (storage capacity was set to 20MB)
I copy a 10MB file which would take space used up to 25MB, passed the storage capacity I'd set (so I expect the FS to extend), and I get an "out of space error - you must delete some files"
I don't delete any files, and just try to do the copy operation again, and now it works fine.
It's almost as if the extension of the filesystem either didnt happen fast enough, when I tried to copy past the actual 20MB storage capacity the first time, or XP couldnt handle this.
The closest I could find on the forums was that the extention was not happening fast enough
Is there a fix for this, either on Windows, or on the Celerra, or am I just missing something ?
Thanks for your help
sebbyr
99 Posts
0
July 1st, 2010 08:00
Good Morning Failel.
Per EMC Documentation:
Managing Celerra Volumes and File Systems with AVM
P/N 300-004-148
REV A07
In a CIFS environment, the CIFS/Windows Microsoft client does Persistent Block Reservation (PBR) to reserve the space before the writes begin. As a result,the file system full error occurs before the HWM is reached and before automatic extension is initiated.
The above can cause an error message indicating the failure of automatic extension start, and a full file system.
Alleviate this timing issue by lowering the HWM on a file system to ensure automatic extension can accommodate normal file system activity. Set the HWM to allow enough free space in the file system to accommodate write operations to the largest average file in that file system. For example,if you have a file system that is 100 GB, and the largest average file in that file system is 20 GB, set the HWM for automatic extension to 70%.
Changes made to the 20 GB file might cause the file system to reach the HWM, or 70 GB. There is 30 GB of space left in the file system to handle the file changes, and to initiate and complete automatic extension withoutfailure.
Please let me know if this answers your question. I have also attached the document for you.
Thanks.
1 Attachment
MgVolFSA.pdf
Rainer_EMC
4 Operator
•
8.6K Posts
1
July 1st, 2010 07:00
Yes - for small file systems it can happen that the fs extension isn't fast enough
fix would be to lower the HWM
Rainer
faisalchoudry
53 Posts
0
July 1st, 2010 09:00
yup that's done it.
Had an end user call up with the problem, with much bigger file systems, so I just built the same scenario in the office, that's why my filesystems are so small.
In my example, I've had to take the HWM to 50 (lowest setting), wouldn't work at 60, but 50 seems to have done the trick.
I see your point about the 90HWM causing a problem on a small filesystem, 10 percent left over I guess doesn't give the celerra enough time to extend. Although Customers site were large filesystems.
Anyway thanks again - I owe you both a drink..
Regards
Faisal Choudry
Email: faisal.choudry@magirus.com
Phone: 01344 401598
(Sent from Blackberry).