File deletion and truncation using a zombie file space
원문보기
IPC분류정보
국가/구분
United States(US) Patent
등록
국제특허분류(IPC7판)
G06F-012/00
G06F-017/30
출원번호
US-0868189
(2004-06-15)
등록번호
US-7451165
(2008-11-11)
발명자
/ 주소
Chen,Ray
Edwards,John
Patel,Kayuri
출원인 / 주소
Network Appliance, Inc.
대리인 / 주소
Blakely, Sokoloff, Taylor & Zafman LLP
인용정보
피인용 횟수 :
0인용 특허 :
63
초록▼
A method and system for reliably performing extra-long operations in a reliable state-full system (such as a file system). The file system includes a separate portion of the file system reserved for files having extra-long operations in progress, including file deletion and file truncation. This sep
A method and system for reliably performing extra-long operations in a reliable state-full system (such as a file system). The file system includes a separate portion of the file system reserved for files having extra-long operations in progress, including file deletion and file truncation. This separate portion of the file system is called the zombie file space; it includes a separate name space from the regular ("live") file system that is accessible to users, and is maintained as part of the file system when recording a consistency point.
대표청구항▼
The invention claimed is: 1. A method of operating a file server, comprising the steps of: identifying a file in a first file space for truncation; in response to a determination that the size of the file is over a threshold, using zombie file space for truncation of the file, the zombie file space
The invention claimed is: 1. A method of operating a file server, comprising the steps of: identifying a file in a first file space for truncation; in response to a determination that the size of the file is over a threshold, using zombie file space for truncation of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, the zombie file space inaccessible to one or more system users, wherein using the zombie file space for truncation of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for truncation; truncating said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 2. The method of claim 1, wherein the step of identifying comprises: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 3. The method of claim 2, wherein the step of truncating is performed after the step of linking and before the step of delinking. 4. A method of operating a file server, comprising the steps of: identifying a file in a first file space for deletion; in response to a determination that the size of the file is over a threshold, using zombie file space for deletion of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, zombie file space inaccessible to one or more system users, wherein using the zombie file space for deletion of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for deletion; deleting said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 5. The method of claim 4, wherein the step of identifying comprises: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 6. The method of claim 5, wherein the step of deleting is performed after the step of linking and before the step of delinking. 7. The method of claim 5, wherein said file is a composite file comprising one or more attached data elements. 8. The method of claim 7, wherein the step of deleting comprises: deleting at least one of the one or more attached data elements after the step of linking and before the step of delinking; and deleting said file after the step of delinking. 9. A file server, comprising: a processor; memory storing program code; a network interface; and mass storage; wherein said processor executes the program code stored in said memory to control access to said mass storage, the program code comprising instructions that, when executed by the processor, cause the server to perform the steps of: identifying a file in a first file space for truncation; in response to a determination that the size of the file is over a threshold, using zombie file space for truncation of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, the zombie file space inaccessible to one or more system users, wherein using the zombie file space for truncation of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for truncation; truncating said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 10. The server of claim 9, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of identifying: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 11. The server of claim 10, wherein the server performs the step of truncating after the step of linking and before the step of delinking. 12. A file server, comprising: a processor; memory storing program code; a network interface; and mass storage; wherein said processor executes the program code stored in said memory to control access to said mass storage, the program code comprising instructions that, when executed by the processor, cause the server to perform the steps of: identifying a file in a first file space for deletion; in response to a determination that the size of the file is over a threshold, using zombie file space for deletion of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, the zombie file space inaccessible to one or more system users, wherein using the zombie file space for deletion of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file spaceafter said file is identified for deletion; deleting blocks of said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 13. The server of claim 12, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of identifying: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 14. The server of claim 13, wherein the server performs the step of deleting after the step of linking and before the step of delinking. 15. The method of claim 13, wherein said file is a composite file comprising one or more attached data elements. 16. The method of claim 15, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of deleting: deleting at least one of the one or more attached data elements after the step of linking and before the step of delinking; and deleting said file after the step of delinking. 17. A computer-readable storage medium storing program code that, when performed by a processor of a file server, causes the server to perform the steps of: identifying a file in a first file space for truncation; in response to a determination that the size of the file is over a threshold, using the zombie file space for truncation of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, zombie file space inaccessible to one or more system users, wherein using the zombie file space for truncation of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for truncation; truncating said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 18. The computer-readable storage medium of claim 17, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of identifying: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 19. The computer-readable storage medium of claim 18, wherein the server performs the step of truncating after the step of linking and before the step of delinking. 20. A computer-readable storage medium storing program code that, when performed by a processor of a file server, causes the server to perform the steps of: identifying a file in a first file space for deletion; in response to a determination that the size of the file is over a threshold, using the zombie file space for deletion of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, zombie file space inaccessible to one or more system users, wherein using the zombie file space for deletion of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for deletion; deleting blocks of said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space. 21. The computer storage medium of claim 20, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of identifying: receiving a selection of said file from a user; and identifying said file for truncation using the zombie file space based on parameter-based file size comparison. 22. The computer readable storage medium of claim 21, wherein the server performs the step of deleting after the step of linking and before the step of delinking. 23. The computer readable storage medium of claim 21, wherein said file is a composite file comprising one or more attached data elements. 24. The computer readable storage medium of claim 23, wherein the instructions, when executed by the processor, cause the server to perform at least the following steps in the course of performing the step of deleting: deleting at least one of the one or more attached data elements after the step of linking and before the step of delinking; and deleting said file after the step of delinking. 25. A computer-readable storage medium storing program code that, when performed by a processor of a file server, causes the server to perform the steps of: identifying a file in a first file space for deletion, the file being a composite file comprising one or more attached data elements; in response to a determination that the size of the file is over a threshold, using zombie file space for deletion of the file, the zombie file space reserved for in progress file operations that takes a long time relative to an interval between consistency points of the file server, the zombie file space inaccessible to one or more system users, wherein using the zombie file space for deletion of the file further comprises: making said file unavailable to the one or more system users in the first file space; linking said file to the zombie file space after said file is identified for deletion; deleting blocks of said file while maintaining file consistency at each consistency point; delinking said file from said zombie file space; and making said file available to the one or more system users in said first file space, wherein in the course of performing the step of deleting, the server is caused to further perform the steps of: deleting at least one of the one or more attached data elements of said file after the step of linking and before the step of delinking; and deleting said file after the step of delinking.
연구과제 타임라인
LOADING...
LOADING...
LOADING...
LOADING...
LOADING...
이 특허에 인용된 특허 (63)
Winterbottom Philip S. (Gillette NJ), Apparatus and methods for making a portion of a first name space available as a portion of a second name space.
Bennett Robert Bradley (Endwell NY) Nugent Robert Michael (Nichols NY) Showalter James Michael (Endicott NY), Computer file management and backup system.
Dunphy William E. (Westminster CO) Halladay Steven M. (Louisville CO) Moy Michael E. (Lafayette CO) Munro Frederick G. (Broomfield CO), Data storage and protection system.
Blickenstaff Ronald L. ; Brant Catherine Irlam ; Dodd Paul David ; Kirchner Anton H. ; Montez Jennifer Kay ; Trede Brian Eldred ; Winter Richard Allen, Data storage management for network interconnected processors.
Belsan Jay S. (Nederland) Rudeseal George A. (Boulder) Milligan Charles A. (Golden) Pedersen Mogens H. (Longmont CO) Kitchen John F. (Lindfield AUX) Ludlam Henry S. (Longmont CO), Deleted data file space release system for a dynamically mapped virtual data storage subsystem.
Haskin,Roger L.; Sawdon,Wayne A.; Schmuck,Frank B.; Wyllie,James C., Ditto address indicating true disk address for actual data blocks stored in one of an inode of the file system and subsequent snapshot.
Eshel Marc M. (Tarrytown NY) Hunt Guerney D. H. (Ithaca NY) Jones Donald N. (Vestal NY) Meyer Christopher (Vestal NY) Schwartz Frederick A. (Binghamton NY), File manager for files shared by heterogeneous clients.
Belsan Jay S. (Nederland CO) Laughlin Jeffrey S. (Nederland CO) Pedersen Mogens H. (Longmont CO) Raicer Robert J. (Niwot CO) Rudeseal George A. (Boulder CO) Schafer Charles P. (Louisville CO) Steele , File server having snapshot application data groups.
Humlicek, Donald R.; DeKoning, Rodney A.; Delaney, William P., Managing a snapshot volume or one or more checkpoint volumes with multiple point-in-time images in a single repository.
Zayas, Edward R.; Susarla, Sai Rama Krishna, Method and apparatus for implementing a highly efficient, robust modified files list (MFL) for a storage system volume.
Jacobs Lawrence ; Adunuthula Seshu ; Anand Mala, Method and apparatus for performing transactions in a stateless web environment which supports a declarative paradigm.
Luis Felipe Cabrera ; Chandrasekaran Mohan ; Inderpal Singh Narang, Method and means for backup and restoration of a database system linked to a system for filing data.
Iwamoto Kouji (Yokohama JPX) Yamaguchi Kota (Yamato JPX) Murakata Yasushi (Yokohama JPX), Method and system for dynamically and asynchronously expanding a file in a on-line database system without suppression o.
McCown Patricia M. (Cresskill NJ) Conway Timothy J. (Highland Park NJ) Jessen Karl M. (Bayonne NJ), Methods and apparatus for monitoring system performance.
Rogers Lawrence D. (13644 Boquita Dr. Del Mar CA 92014) Wellington-Oguri Roger (7931 Nightingale Way San Diego CA 92123), Network policy implementation system for performing network control operations in response to changes in network state.
Bradshaw Paul Lawrence ; Cannon David Maxwell ; Hineman Wayne Curtis ; Kaczmarski Michael Allen ; Rees Robert Michael, Reconfiguration an aggregate file including delete-file space for optimal compression.
Barnes Cherie C. (Barton NY) Bennett Robert B. (Endwell NY) Szczygielski Thomas J. (Endicott NY), Space management system for data files having shared access.
Tevis Gregory J. (Tucson AZ) Waldo Ellen J. (Tucson AZ), Storage management of a first file system using a second file system containing surrogate files and catalog management i.
Cutler David N. (Bellevue WA) Kelly ; Jr. James W. (Redmond WA) Perazzoli ; Jr. Frank L. (Redmond WA 4), System and method for adding new waitable object types to object oriented computer operating system.
Ault Michael B. (Austin TX) Plassmann Ernst R. (Pflugerville TX) Rich Bruce A. (Round Rock TX) Wilkes Michael D. (Austin TX), System and method for supporting file attributes on a distributed file system without native support therefor.
Takasaki Shigeo (Sagamihara JPX) Yoshioka Masaichiro (Sagamihara JPX) Kubo Takashige (Hachioji JPX) Ukai Yoshio (Yokohama JPX) Kubo Yasuo (Yokohama JPX) Imura Jinichi (Yokosuka JPX) Hagiwara Nobutaka, Virtual machine file control system which translates block numbers into virtual addresses then into real addresses for a.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.