Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
I deleted 80 TB to copy new data's 72TB but I cannot copy those 72TB , my storage is already full.
My storage is already full and I need to have free space in order to write some new data
I informed the customer about the delay of displaying the free space:
After deleting the files the file system of 5500 V3 devices reclaims space in the background no need a command line. After files are deleted, they queue up in the background for release. In addition, there is a delay (approximately 20s) for the file system to display its available space.
The example is related below:
-If large files are deleted, their occupied space must be reclaimed multiple times
-If small files are deleted, a maximum of 1000 files can be deleted per second. Their space will be released only after the size of deleted files reaches 32 MB
the solution is regarding the file system that was deleted , it was made with 8KB and the new file system who was created was made with 64KB.
The client need to create the new file with 64KB block size the same like the first file system, if not, you will receive a message that the space is nor sufficient.
the step that must be done when a similar case appear:
-please ask for the logs and check the block size of the file system