US7415480B2 - System and method for providing programming-language-independent access to file system content - Google Patents
System and method for providing programming-language-independent access to file system content Download PDFInfo
- Publication number
- US7415480B2 US7415480B2 US10/732,727 US73272703A US7415480B2 US 7415480 B2 US7415480 B2 US 7415480B2 US 73272703 A US73272703 A US 73272703A US 7415480 B2 US7415480 B2 US 7415480B2
- Authority
- US
- United States
- Prior art keywords
- file
- file system
- identity
- given
- virtual
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
Definitions
- This invention relates to computer systems and, more particularly, to file-based storage systems.
- Computer systems often process large quantities of information, including application data and executable code configured to process such data.
- computer systems provide various types of mass storage devices configured to store data, such as magnetic and optical disk drives, tape drives, etc.
- mass storage devices configured to store data
- storage devices are frequently organized into hierarchies of files by software such as an operating system.
- an operating system Often a file defines a minimum level of data granularity that a user can manipulate within a storage device, although various applications and operating system processes may operate on data within a file at a lower level of granularity than the entire file.
- various types of information about files may be stored in addition to the files themselves.
- metadata information about files
- access to files and their metadata by application software is provided by an interface specific to a particular programming language, operating system, or hardware architecture.
- a separate interface may need to be provided for applications using a new programming language, operating system, or hardware architecture to be given access to files and metadata.
- Creating and supporting new interfaces may require additional programmer effort, such as coding and verification effort. Further, as types of interfaces multiply, the effort required to maintain them over time increases. Additionally, if a unique interface is provided for each programming language, operating system, or architecture scenario, such interfaces may diverge considerably in their support for various features of file and metadata access. For example, not all interfaces may provide all programming languages the same level of access to file data and metadata. Such divergence among interfaces may complicate the application programming task and hinder acceptance of a given file format among developers.
- the system may include a storage device configured to store a plurality of files and a file system configured to manage access to the storage device and to store file system content.
- the file system may include a programming-language-independent interface whereby an application accesses the file system content.
- the programming-language-independent interface may be configured to detect a virtual file identity corresponding to a given file, select at least a portion of the file system content dependent on the virtual file identity, and return the selected file system content.
- the virtual file identity may be formed by embedding a command token within a file identity corresponding to the given file, while in another embodiment of this implementation, the virtual file identity may be formed by prepending a virtual directory to a file identity corresponding to the given file.
- a method is also contemplated which, in one embodiment, may include storing file system content and accessing the file system content via a programming-language-independent interface.
- FIG. 1 is a block diagram illustrating one embodiment of a storage system.
- FIG. 2 is a block diagram illustrating one embodiment of an operating system architecture and its interface to storage devices.
- FIG. 3 is a block diagram illustrating one embodiment of a file system configured to store file system content.
- FIG. 4 is a flow diagram illustrating one embodiment of a method of accessing file system content via a programming-language-independent interface.
- storage system 10 includes a plurality of host devices 20 a and 20 b coupled to a plurality of storage devices 30 a and 30 b via a system interconnect 40 .
- host device 20 b includes a system memory 25 in the illustrated embodiment.
- elements referred to herein by a reference number followed by a letter may be referred to collectively by the reference number alone.
- host devices 20 a and 20 b and storage devices 30 a and 30 b may be referred to collectively as host devices 20 and storage devices 30 .
- host devices 20 may be configured to access data stored on one or more of storage devices 30 .
- storage system 10 may be implemented within a single computer system, for example as an integrated storage server.
- host devices 20 may be individual processors
- system memory 25 may be a cache memory such as a static RAM (SRAM)
- storage devices 30 may be mass storage devices such as hard disk drives or other writable or rewritable media
- system interconnect 40 may include a peripheral bus interconnect such as a Peripheral Component Interface (PCI) bus.
- PCI Peripheral Component Interface
- system interconnect 40 may include several types of interconnect between host devices 20 and storage devices 30 .
- system interconnect 40 may include one or more processor buses (not shown) configured for coupling to host devices 20 , one or more bus bridges (not shown) configured to couple the processor buses to one or more peripheral buses, and one or more storage device interfaces (not shown) configured to couple the peripheral buses to storage devices 30 .
- Storage device interface types may in various embodiments include the Small Computer System Interface (SCSI), AT Attachment Packet Interface (ATAPI), Firewire, and/or Universal Serial Bus (USB), for example, although numerous alternative embodiments including other interface types are possible and contemplated.
- storage system 10 may be configured to provide most of the data storage requirements for one or more other computer systems (not shown), and may be configured to communicate with such other computer systems.
- storage system 10 may be configured as a distributed storage system, such as a storage area network (SAN), for example.
- host devices 20 may be individual computer systems such as server systems
- system memory 25 may be comprised of one or more types of dynamic RAM (DRAM)
- storage devices 30 may be standalone storage nodes each including one or more hard disk drives or other types of storage
- system interconnect 40 may be a communication network such as Ethernet or Fibre Channel.
- a distributed storage configuration of storage system 10 may facilitate scaling of storage system capacity as well as data bandwidth between host and storage devices.
- storage system 10 may be configured as a hybrid storage system, where some storage devices 30 are integrated within the same computer system as some host devices 20 , while other storage devices 30 are configured as standalone devices coupled across a network to other host devices 20 .
- system interconnect 40 may encompass a variety of interconnect mechanisms, such as the peripheral bus and network interconnect described above.
- storage system 10 may have an arbitrary number of each of these types of devices in alternative embodiments. Also, in some embodiments of storage system 10 , more than one instance of system memory 25 may be employed, for example in other host devices 20 or storage devices 30 . Further, in some embodiments, a given system memory 25 may reside externally to host devices 20 and storage devices 30 and may be coupled directly to a given host device 20 or storage device 30 or indirectly through system interconnect 40 .
- one or more host devices 20 may be configured to execute program instructions and to reference data, thereby performing a computational function.
- system memory 25 may be one embodiment of a computer-accessible medium configured to store such program instructions and data.
- program instructions and/or data may be received, sent or stored upon different types of computer-accessible media.
- a computer-accessible medium may include storage media or memory media such as magnetic or optical media, e.g., disk or CD-ROM included in storage system 10 as storage devices 30 .
- a computer-accessible medium may also include volatile or non-volatile media such as RAM (e.g.
- a computer-accessible medium may include transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link, which may be included in some embodiments of storage system 10 as system interconnect 40 .
- program instructions and data stored within a computer-accessible medium as described above may implement an operating system that may in turn provide an environment for execution of various application programs.
- a given host device 20 may be configured to execute a version of the Microsoft Windows operating system, the Unix operating system, the Apple Macintosh operating system, or another suitable operating system.
- a given host device may be configured to execute application programs such as word processors, web browsers and/or servers, email clients and/or servers, and multimedia applications, among many other possible applications.
- either the operating system or a given application may generate requests for data to be loaded from or stored to a given storage device 30 .
- code corresponding to portions of the operating system or an application itself may be stored on a given storage device 30 , so in response to invocation of the desired operation system routine or application program, the corresponding code may be retrieved for execution.
- operating system or application execution may produce data to be stored.
- the data structures may include one or more tables configured to store information such as, for example, the identity of each file, its location within storage devices 30 (e.g., a mapping to a particular physical location within a particular storage device), as well as other information about each file as described in greater detail below.
- the control structures may include executable routines for manipulating files, such as, for example, function calls for changing file identity and for modifying file content as described in greater detail below.
- a file system may be integrated into the operating system such that any access to data stored on storage devices 30 is governed by the control and data structures of the file system.
- Different operating systems may implement different native file systems using different formats, but in some embodiments, a given operating system may include a file system that supports multiple different types of file system formats, including file system formats native to other operating systems.
- the various file system formats supported by the file system may be referred to herein as local file systems.
- a file system may be implemented using multiple layers of functionality arranged in a hierarchy, as illustrated in FIG. 2 .
- FIG. 2 illustrates one embodiment of an operating system architecture and its interface to storage devices.
- operating system 200 includes a user space 210 and a kernel space 220 .
- User space 210 includes a plurality of processes 212 A-C, each of which may correspond to a given user application.
- some application processes 212 within user space 210 may be distinct from operating system 200 . Such processes may be said to operate within an environment provided by operating system 200 , or to operate “on top of” operating system 200 .
- Each of processes 212 may be configured to access storage devices 230 A-C through calls to application programming interface (API) 214 .
- API 214 provides processes 212 with access to file system 205 , which is configured to operate within kernel space 220 .
- storage devices 230 may be illustrative of storage devices 30 of FIG. 1 .
- operating system 200 any of its components, and/or any of processes 212 may be configured to execute on one or more host devices 20 of FIG. 1 , for example as program instructions and data stored within a computer-accessible medium such as system memory 25 of FIG. 1 .
- a given host device 20 may reside in a different computer system from a given storage device 30 , and may access that storage device via a network.
- a given process such as process 212 A may execute remotely and may access storage devices 230 over a network.
- file system 200 includes network protocols 225 to support access to the file system by remote processes.
- network protocols 225 may include support for the Network File System (NFS) protocol or the Common Internet File System (CIFS) protocol, for example, although it is contemplated that any suitable network protocol may be employed, and that multiple such protocols may be supported in some embodiments.
- NFS Network File System
- CIFS Common Internet File System
- File system 205 may be configured to support a plurality of local file systems.
- file system 205 includes a VERITAS (VxFS) format local file system 240 A, a fast file system (FFS) format local file system 240 B, and a proprietary (X) format local file system 240 X.
- VxFS VERITAS
- FFS fast file system
- X proprietary
- file system 205 includes a virtual file system 222 .
- virtual file system 222 may be configured to translate file system operations originating from processes 212 to a format applicable to the particular local file system 240 targeted by each operation.
- operating system 200 includes device drivers 224 through which local file systems 240 may access storage devices 230 .
- Device drivers 224 may implement data transfer protocols specific to the types of interfaces employed by storage devices 230 .
- device drivers 224 may provide support for transferring data across SCSI and ATAPI interfaces, though in other embodiments device drivers 224 may support other types and combinations of interfaces.
- file system 205 also includes filter driver 221 .
- filter driver 221 may be configured to monitor each operation entering file system 205 and, subsequent to detecting particular types of operations, to cause additional operations to be performed or to alter the behavior of the detected operation. For example, in one embodiment filter driver 221 may be configured to combine multiple write operations into a single write operation to improve file system performance. In another embodiment, filter driver 221 may be configured to compute a signature of a file subsequent to detecting a write to that file. In still another embodiment, filter driver 221 may be configured to store information, such as records, associated with particular files subsequent to detecting certain kinds of operations on those files, as described in greater detail below. It is contemplated that in some embodiments, filter driver 221 may be configured to implement one or more combinations of the aforementioned operations, including other filter operations not specifically mentioned.
- filter driver 221 is part of file system 205 and not an application or process within user space 210 . Consequently, filter driver 221 may be configured to operate independent of applications and processes within the user space 210 . Alternatively, or in addition to the above, filter driver 221 may be configured to perform operations in response to requests received from applications or processes within the user space 210 .
- kernel space 220 may include processes (not shown) that generate accesses to storage devices 230 , similar to user space processes 212 .
- processes executing in kernel space 220 maybe configured to access file system 205 through a kernel-mode API (not shown), in a manner similar to user space processes 212 .
- all accesses to storage devices 230 may be processed by file system 205 , regardless of the type or space of the process originating the access operation.
- operating system 200 and file system 205 may support different numbers and formats of local file systems 240 , or only a single local file system 240 .
- network protocol 225 may be omitted or integrated into a portion of operating system 200 external to file system 205 .
- virtual file system 222 may be omitted or disabled, for example if only a single local file system 240 is in use.
- filter driver 221 may be implemented within a different layer of file system 205 .
- filter driver 221 may be integrated into virtual file system 222 , while in another embodiment, an instance of filter driver 221 may be implemented in each of local file systems 240 .
- file system 205 may be configured to manage access to a plurality of files stored on storage devices 230 .
- each stored file may have an associated identity used by the file system to distinguish each file from other files.
- the identity of a file may be a file name, which may for example include a string of characters such as “filename.txt”.
- file system 205 that implement a file hierarchy, such as a hierarchy of folders or directories, all or part of the file hierarchy may be included in the file identity. For example, a given file named “file1.txt” may reside in a directory “smith” that in turn resides in a directory “users”.
- the directory “users” may reside in a directory “test1” that is a top-level or root-level directory within file system 205 .
- file system 205 may define a single “root directory” to include all root-level directories, where no higher-level directory includes the root directory.
- multiple top-level directories may coexist such that no higher-level directory includes any top-level directory.
- the names of the specific folders or directories in which a given file is located may be referred to herein as the given file's path or path name.
- a given file's identity may be specified by listing each directory in the path of the file as well as the file name. Referring to the example given above, the identity of the given instance of the file named “file1.txt” may be specified as “/test1/users/smith/file1.txt”. It is noted that in some embodiments of file system 205 , a file name alone may be insufficient to uniquely identify a given file, whereas a fully specified file identity including path information may be sufficient to uniquely identify a given file. There may, for example, exist a file identified as “/test2/users/smith/file1.txt” that, despite sharing the same file name as the previously mentioned file, is distinct by virtue of its path.
- the files managed by file system 205 may store application data or program information, which may collectively be referred to as file data, in any of a number of encoding formats.
- a given file may store plain text in an ASCII-encoded format or data in a proprietary application format, such as a particular word processor or spreadsheet encoding format.
- a given file may store video or audio data or executable program instructions in a binary format. It is contemplated that numerous other types of data and encoding formats, as well as combinations of data and encoding formats, may be used in files as file data.
- file system 205 may be configured to store information corresponding to one or more given files, which information may be referred to herein as metadata.
- metadata may encompass any type of information associated with a file.
- metadata may include information such as (but not limited to) the file identity, size, ownership, and file access permissions.
- Metadata may also include free-form or user-defined data such as records corresponding to file system operations, as described in greater detail below. Metadata corresponding to a file as well as the data content of files may collectively be referred to herein as file system content.
- FIG. 3 illustrates one embodiment of a file system configured to store file system content.
- the embodiment of file system 205 shown in FIG. 3 may include those elements illustrated in the embodiment of FIG. 2 ; however, for sake of clarity, some of these elements are not shown.
- file system 205 includes filter driver 221 , an arbitrary number of files 310 a - n , and a respective named stream 320 a - n associated with each of files 310 a - n .
- Filter driver 221 includes programming language independent interface 305 .
- files 310 a - n or named streams 320 a - n may be referred to respectively as a file 310 or a named stream 320
- files 310 a - n and named reams 320 a - n may be referred to collectively as files 310 and named streams 320 , respectively.
- files 310 and named streams 320 may collectively be referred to as file system content.
- Files 310 may be representative of files managed by file system 205 , and may in various embodiments be configured to store various types of data and program instructions as described above.
- each of files 310 has a corresponding named stream 320 .
- Each of named streams 320 may be configured to store metadata pertaining to its corresponding file. It is noted that files 310 and named streams 320 may be physically stored on one or more storage devices, such as storage devices 230 of FIG. 2 . However, for purposes of illustration, files 310 and named streams 320 are shown as conceptually residing within file system 205 .
- filter driver 221 may be configured to access file data stored in a given file 310 .
- filter driver 221 may be configured to detect read and/or write operations received by file system 205 , and may responsively cause file data to be read from or written to a given file 310 corresponding to the received operation.
- filter driver 221 may be configured to generate metadata corresponding to a given file 310 and store the generated metadata in the corresponding named stream 320 .
- filter driver 221 may be configured to update metadata corresponding to the last modified time of given file 310 and to store the updated metadata within named stream 320 .
- filter driver 221 may be configured to retrieve metadata corresponding to a specified file on behalf of a particular application.
- Metadata also may be generated in response to various types of file system activity initiated by operating system 200 or processes 212 of FIG. 2 .
- the generated metadata may include records of arbitrary complexity.
- filter driver 221 may be configured to detect various types of file manipulation operations such as file create, delete, rename, and/or copy operations as well as file read and write operations. After detecting a particular file operation, filter driver 221 may be configured to generate a record of the operation and store the record in the appropriate named stream 320 as metadata of the file 310 targeted by the operation.
- the stored metadata record may in various embodiments include various kinds of information about the file 310 and the operation detected, such as the identity of the process generating the operation, file identity, file type, file size, file owner, and/or file permissions, for example.
- the record may include a file signature indicative of the content of file 310 .
- a file signature may be a hash-type function of all or a portion of the file contents and may have the property that minor differences in file content yield quantifiably distinct file signatures.
- the file signature may employ the Message Digest 5 (MD5) algorithm, which may yield different signatures for files differing in content by as little as a single bit, although it is contemplated that any suitable signature-generating algorithm may be employed.
- MD5 Message Digest 5
- the record may also include additional information not specifically listed.
- the metadata record stored by filter driver 221 subsequent to detecting a particular file operation may be generated and stored in Extensible Markup Language (XML) format, although it is contemplated that in other embodiments, any suitable format may be used.
- XML-format records may allow arbitrary definition of record fields, according to the desired metadata to be recorded.
- One example of an XML-format record is as follows:
- the number associated with the “record sequence” field indicates that this record is the first record associated with file 310 a .
- the “path” field includes the file identity, and the “type” field indicates the file type, which in one embodiment may be provided by the process issuing the file create operation, and in other embodiments may be determined from the extension of the file name or from header information within the file, for example.
- the “user id” field records both the numerical user id and the textual user name of the user associated with the process issuing the file create operation, and the “group id” field records both the numerical group id and the textual group name of that user.
- the “perm” field records file permissions associated with file 310 a in a format specific to the file system 205 and/or the operating system.
- the “md5” field records an MD5 signature corresponding to the file contents, and the “size” field records the length of file 310 a in bytes.
- filter driver 221 may store records corresponding to detected operations where the records include more or fewer fields, as well as fields having different definitions and content. It is also contemplated that in some embodiments filter driver 221 may encapsulate data read from a given file 310 within the XML format, such that read operations to files may return XML data regardless of the underlying file data format.
- filter driver 221 may be configured to receive XML format data to be written to a given file 310 . In such an embodiment, filter driver 221 may be configured to remove XML formatting prior to writing the file data to given file 310 .
- metadata may be stored in a structure other than a named stream.
- metadata corresponding to one or more files may be stored in another file in a database format or another format.
- other software modules or components of file system 205 may be configured to generate, store, and/or retrieve metadata.
- the metadata function of filter driver 221 may be incorporated into or duplicated by another software module.
- file system 205 may be configured to store various types of file system content.
- File system 205 may store numerous types of file data within one or more files, and may store metadata of arbitrary complexity corresponding to a given file.
- File system 205 may also be configured to consume metadata.
- file system 205 may implement particular storage policies whereby files having certain usage characteristics as indicated in their metadata are assigned to particular types of storage. In one embodiment, for example, files that are more recently used or are accessed by certain types of processes may be assigned to faster types of storage, whereas other files may be assigned to slower storage.
- application or operating system processes external to file system 205 may also be configured to access file system content.
- a programmer writing an application software module may wish to create and manipulate specific files and their associated file data in order to store or retrieve application data. Additionally, such a programmer may wish to perform actions contingent on the metadata characteristics of certain files, such as configuring a backup program to select only files that have been modified since the time of the last backup.
- API 214 of FIG. 2 may provide an interface of function calls whereby an application process 212 may interact with file system 205 to interact with file system content.
- API 214 consists of language-specific interfaces, such as library or stub files that are written to interface with applications coded in particular languages, such as C or Java, for example. Supporting applications written in languages other than those supported by the existing API 214 may require the coding of an additional API targeted to the desired language.
- APIs may reflect specific underlying characteristics of operating systems or hardware architectures, and in some instances where file system 205 supports interfaces to different operating systems or architectures, multiple APIs may be required even for the same target application language. For example, some hardware architectures may use different byte ordering conventions (e.g., “endianness”) for data storage, requiring API libraries and/or stub files conforming to each desired byte ordering convention.
- the metadata stored by file system 205 may be arbitrarily extensible to cover many different types of information.
- providing specific support in API 214 for each possible type of arbitrary record that may be stored as metadata may significantly complicate the coding and maintenance of API 214 .
- filter driver 221 includes programming language independent interface 305 , which may also be referred to herein as interface 305 .
- Interface 305 may be configured to provide a protocol whereby a given software application may access file system content, such as file data or metadata corresponding to a given file, independently of the programming language or format of the application or the associated API.
- interface 305 may allow any software application capable of accessing a file to access any file data included in or metadata associated with that file, regardless of programming language issues or the specific metadata requested. It is contemplated that that in some embodiments, interface 305 may be implemented externally to filter driver 221 or incorporated into a different module or process of file system 205 .
- interface 305 may be configured to examine the various file operations processed by filter driver 221 to detect whether a given operation specifies a virtual file identity, and to select and return corresponding metadata of a given file identity dependent on the virtual file identity.
- a virtual file identity may be constructed for any given file identity defined within file system 205 by adding information to the given file identity according to a particular format or protocol.
- a virtual file identity may not literally specify a particular file within file system 205 , but may instead represent a semantic “overloading” of a file identity that does specify such a particular file.
- a format for forming a virtual file identity includes embedding a command token within a given file identity.
- the command token may include a string of characters that specify a type of file system content to be accessed with respect to the given file identity.
- a command token may take the form of the string “$cas:cmd:” inserted into the file identity just prior to the file name, where the cmd field indicates one or more of several possible types of file system content to be accessed.
- command tokens such as “rddata” may include other arguments, for example, parameters specifying a location at which to begin accessing file data as well as a quantity of data to be accessed.
- a “rddata(345, 100)” command token may be configured to cause 100 bytes of file data to be read from the specified file, beginning at byte 345 of the file.
- a corresponding virtual file identity may be “/test1/users/smith/$cas:meta:file1.txt”, where “meta” is defined as a cmd field value that selects all metadata associated with the file. Numerous other types of cmd field values are possible and contemplated, dependent upon the file system content defined by file system 205 .
- command token may be any suitable string and may be inserted at any desired point in the file identity in forming the virtual file identity.
- a given virtual file identity formed by embedding a command token within a given file identity may collide with another existing file identity within file system 205 .
- file system 205 may actually exist within file system 205 a file identity identical to the virtual file identity “/test1/users/smith/$cas:meta:file1.txt”. This ambiguity may be resolved by convention, where the various applications interacting with file system 205 avoid using the various possible command tokens within the file identity when a virtual file identity is not intended.
- file system 205 may be configured to treat command tokens as reserved, such that only virtual file identities may include them.
- a virtual file identity may be formed by prepending a virtual directory to the path of the given file specified in the given file's file identity.
- the virtual directory may specify a top-level directory that is not visible to conventional path-listing functions of file system 205 ; that is, if a user or application were to attempt to perform a directory listing of a virtual directory, the virtual directory would not appear to exist, and a corresponding error or warning might be generated.
- one example of forming a virtual file identity by prepending a virtual directory is “/cas/test1/users/smith/file1.txt”, where the virtual directory is “/cas”.
- all metadata associated with the file identity may be returned.
- a number of virtual directories of the format “/cas/cmd” may be employed, where the cmd field indicates one or more of several possible types of metadata to be accessed as described above. If in such an embodiment only the MD5 signature corresponding to the file identity were desired, for example, the corresponding virtual file identity may be formed as “/cas/md5x/test1/users/smith/file1.txt”. Numerous other types of virtual directory specifications and cmd field values are possible and contemplated, as noted above.
- any virtual file identity formed using that virtual directory may be guaranteed to be unique. Collisions between virtual file identities and existing file identities may thereby be avoided.
- interface 305 may be configured to recognize only one format of virtual file identity, while in other embodiments interface 305 may recognize any of a number of such formats. Regardless of the virtual file identity format used, in one embodiment interface 305 may be configured to examine or monitor the various file operations received by filter driver 221 to determine whether such operations specify virtual file identities. If interface 305 detects a virtual file identity corresponding to a given file identity, it may be configured to select file system content indicated by the virtual file identity, and subsequently to return the selected content to the application or process issuing the file operation.
- file system 205 may receive from a process 212 a file operation specifying a virtual file identity corresponding to a given file 310 that indicates that all or some portion of metadata should be returned.
- interface 305 may be configured to directly or indirectly access corresponding named stream 320 and to select all or part of the metadata stored therein, dependent on the virtual file identity.
- the virtual file identity may specify only a particular subset of metadata, as described above.
- the selected metadata may then be returned to process 212 , which may correspond to a user application, for example.
- file identity formats are determined by a file system such as file system 205 . Consequently, a given file identity is consistent regardless of the type of process or application accessing it or the programming language of that process or application. Since a virtual file identity is used to specify access to metadata in a manner similar to ordinary access to files by file identity as described above, interface 305 may operate to provide access to such metadata independently of the programming language of the requesting application.
- the operation may be processed according to the indication of the virtual file identity regardless of the type of file operation specified. That is, the specification of a virtual file identity in a file operation by an application or process may override other behavior specified by the file operation. For example, in one embodiment applications may be only allowed read access to metadata via a virtual file identity. In such an embodiment, if a given application issued a file write operation specifying a virtual file identity indicating that metadata were to be accessed, the write behavior may be disregarded by interface 305 , and metadata may be read and returned as indicated by the virtual file identity. In other embodiments, attempts to access read-only metadata using a file write operation may be disallowed, and an error condition may or may not occur.
- interface 305 allows programming-language-independent access to any file system content, in some embodiments a given application need not implement specific individual system calls for file read and write operations. Rather, in such embodiments, a generic system call may be implemented that allows an application to pass a virtual file identity to file system 205 . Interface 305 may then process the virtual file identity to determine the type of file system content to be returned.
- FIG. 4 illustrates one embodiment of a method of accessing file system content via a programming-language-independent interface.
- operation begins in block 400 where file system content, such as file data or metadata corresponding to a given file, is stored.
- file system content such as file data or metadata corresponding to a given file
- filter driver 221 may be configured to store metadata in a named stream 320 corresponding to a given file 310 subsequent to detecting a particular file operation on given file 310 .
- a given application or process may generate a file operation using a virtual file identity corresponding to the given file (block 402 ).
- the virtual file identity may be formed by embedding a command token within the file identity corresponding to the given file, as described above.
- the virtual file identity may be formed by prepending a virtual directory to the file identity corresponding to the given file, also as described above.
- the virtual file identity may then be detected by a programming-language-independent interface (block 404 ).
- a programming-language-independent interface For example, in one embodiment, after a given process 212 generates the file operation specifying a given virtual file identity, the operation may be received by file system 205 via API 214 . Filter driver 221 may process the file operation, and interface 305 may detect the virtual file identity.
- At least a portion of the file system content may be selected dependent on the virtual file identity (block 406 ).
- the virtual file identity may specify that all or only a particular subset of metadata corresponding to a given file is desired, such as by specifying a particular command token or virtual directory.
- file data included the given file may be selected.
- interface 305 may place selected file data or metadata in a buffer and return a pointer to the buffer to given process 212 via file system 205 and API 214 .
- Other methods by which return of the selected metadata may be coordinated are possible and contemplated.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
<record sequence=“1”> |
<path>/test1/foo.pdf</path> | |
<type>application/pdf</type> | |
<user id=1598>username</user> | |
<group id=119>groupname</group> | |
<perm>rw-r--r--</perm> | |
<md5>d41d8cd98f00b204e9800998ecf8427e</md5> | |
<size>0</size> |
</record> | ||
Such a record may be appended to the named stream (for example, named
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/732,727 US7415480B2 (en) | 2003-12-10 | 2003-12-10 | System and method for providing programming-language-independent access to file system content |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/732,727 US7415480B2 (en) | 2003-12-10 | 2003-12-10 | System and method for providing programming-language-independent access to file system content |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050131955A1 US20050131955A1 (en) | 2005-06-16 |
US7415480B2 true US7415480B2 (en) | 2008-08-19 |
Family
ID=34652933
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/732,727 Active 2025-04-22 US7415480B2 (en) | 2003-12-10 | 2003-12-10 | System and method for providing programming-language-independent access to file system content |
Country Status (1)
Country | Link |
---|---|
US (1) | US7415480B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080126374A1 (en) * | 2003-11-26 | 2008-05-29 | Dhrubajyoti Borthakur | System and method for detecting and storing file identity change information within a file system |
US11087071B2 (en) * | 2019-11-14 | 2021-08-10 | Ciena Corporation | Self-compressed YANG model |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7546354B1 (en) * | 2001-07-06 | 2009-06-09 | Emc Corporation | Dynamic network based storage with high availability |
JP2004280283A (en) * | 2003-03-13 | 2004-10-07 | Hitachi Ltd | Distributed file system, distributed file system server, and access method to distributed file system |
JP4320195B2 (en) | 2003-03-19 | 2009-08-26 | 株式会社日立製作所 | File storage service system, file management apparatus, file management method, ID designation type NAS server, and file reading method |
US7831552B2 (en) * | 2004-06-07 | 2010-11-09 | Symantec Operating Corporation | System and method for querying file system content |
US8306991B2 (en) * | 2004-06-07 | 2012-11-06 | Symantec Operating Corporation | System and method for providing a programming-language-independent interface for querying file system content |
US20070022117A1 (en) * | 2005-07-21 | 2007-01-25 | Keohane Susann M | Accessing file system snapshots directly within a file system directory |
US8447781B2 (en) * | 2005-07-29 | 2013-05-21 | International Business Machines Corporation | Content-based file system security |
WO2012098211A1 (en) * | 2011-01-21 | 2012-07-26 | Technicolor Delivery Technologies | Method for backward-compatible aggregate file system operation performance improvement, and respective apparatus |
US8966211B1 (en) * | 2011-12-19 | 2015-02-24 | Emc Corporation | Techniques for dynamic binding of device identifiers to data storage devices |
US8924682B1 (en) * | 2011-12-29 | 2014-12-30 | Emc Corporation | Method of protecting virtual tape data from accidental loss due to overwriting |
KR102667438B1 (en) * | 2017-01-25 | 2024-05-20 | 삼성전자주식회사 | Electronic device and data management method thereof |
US10693909B2 (en) * | 2018-01-19 | 2020-06-23 | International Business Machines Corporation | Securing an endpoint in a computer network |
US11726273B2 (en) * | 2018-12-21 | 2023-08-15 | Corning Incorporated | Light diffusing multi-fiber design configured for use with UV LEDs |
Citations (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5623657A (en) | 1993-12-30 | 1997-04-22 | International Business Machines Corporation | System for processing application programs including a language independent context management technique |
US6240401B1 (en) | 1998-06-05 | 2001-05-29 | Digital Video Express, L.P. | System and method for movie transaction processing |
US6240429B1 (en) | 1998-08-31 | 2001-05-29 | Xerox Corporation | Using attached properties to provide document services |
US6286013B1 (en) | 1993-04-01 | 2001-09-04 | Microsoft Corporation | Method and system for providing a common name space for long and short file names in an operating system |
US20010025311A1 (en) | 2000-03-22 | 2001-09-27 | Masato Arai | Access control system |
US20020049731A1 (en) | 2000-05-31 | 2002-04-25 | Takuya Kotani | Information processing method and apparatus |
US6389538B1 (en) | 1998-08-13 | 2002-05-14 | International Business Machines Corporation | System for tracking end-user electronic content usage |
US20020184608A1 (en) * | 2001-03-14 | 2002-12-05 | Kuldipsingh Pabla | Method and apparatus for lightweight support on set top box |
US20030093556A1 (en) | 2001-11-10 | 2003-05-15 | Toshiba Tec Kabushiki Kaisha | Document service appliance |
US20030151633A1 (en) | 2002-02-13 | 2003-08-14 | David George | Method and system for enabling connectivity to a data system |
US20030172368A1 (en) | 2001-12-26 | 2003-09-11 | Elizabeth Alumbaugh | System and method for autonomously generating heterogeneous data source interoperability bridges based on semantic modeling derived from self adapting ontology |
US20040002942A1 (en) | 2002-06-28 | 2004-01-01 | Microsoft Corporation | System and method for managing file names for file system filter drivers |
US20040015862A1 (en) * | 2001-05-15 | 2004-01-22 | Dunn Jeffrey J. | Method and apparatus for automatic accessibility assessment |
US20040059866A1 (en) | 2001-06-25 | 2004-03-25 | Kayuri Patel | System and method for representing named data streams within an on-disk structure of a file system |
US20040068480A1 (en) * | 2002-10-08 | 2004-04-08 | Lam Ioi K. | Method and apparatus for initializing romized system classes at virtual machine build time |
US20040078542A1 (en) * | 2002-10-14 | 2004-04-22 | Fuller William Tracy | Systems and methods for transparent expansion and management of online electronic storage |
US20040186857A1 (en) | 2003-03-18 | 2004-09-23 | Apple Computer Inc. | Localized viewing of file system names |
US6799184B2 (en) | 2001-06-21 | 2004-09-28 | Sybase, Inc. | Relational database system providing XML query support |
US6842758B1 (en) | 1999-07-30 | 2005-01-11 | Computer Associates Think, Inc. | Modular method and system for performing database queries |
US20050015461A1 (en) | 2003-07-17 | 2005-01-20 | Bruno Richard | Distributed file system |
US20050038813A1 (en) | 2003-08-12 | 2005-02-17 | Vidur Apparao | System for incorporating information about a source and usage of a media asset into the asset itself |
US20050060561A1 (en) * | 2003-07-31 | 2005-03-17 | Pearson Siani Lynne | Protection of data |
US20050073982A1 (en) * | 2003-10-07 | 2005-04-07 | Accenture Global Services Gmbh. | Connector gateway |
US20050114381A1 (en) | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for generating extensible file system metadata |
US20050114406A1 (en) * | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for detecting and storing file content access information within a file system |
US6976241B2 (en) | 2001-11-14 | 2005-12-13 | Intel Corporation | Cross platform administrative framework |
US20060004759A1 (en) | 2004-06-07 | 2006-01-05 | Veritas Operating Corporation | System and method for file system content processing |
US20060004709A1 (en) | 2004-06-07 | 2006-01-05 | Veritas Operating Corporation | System and method for providing a programming-language-independent interface for querying file system content |
US7350200B2 (en) * | 2001-03-29 | 2008-03-25 | Intel Corporation | Method and system of controlling dynamically compiled native code size |
-
2003
- 2003-12-10 US US10/732,727 patent/US7415480B2/en active Active
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6286013B1 (en) | 1993-04-01 | 2001-09-04 | Microsoft Corporation | Method and system for providing a common name space for long and short file names in an operating system |
US5623657A (en) | 1993-12-30 | 1997-04-22 | International Business Machines Corporation | System for processing application programs including a language independent context management technique |
US6240401B1 (en) | 1998-06-05 | 2001-05-29 | Digital Video Express, L.P. | System and method for movie transaction processing |
US6389538B1 (en) | 1998-08-13 | 2002-05-14 | International Business Machines Corporation | System for tracking end-user electronic content usage |
US6240429B1 (en) | 1998-08-31 | 2001-05-29 | Xerox Corporation | Using attached properties to provide document services |
US6842758B1 (en) | 1999-07-30 | 2005-01-11 | Computer Associates Think, Inc. | Modular method and system for performing database queries |
US20010025311A1 (en) | 2000-03-22 | 2001-09-27 | Masato Arai | Access control system |
US20020049731A1 (en) | 2000-05-31 | 2002-04-25 | Takuya Kotani | Information processing method and apparatus |
US20020184608A1 (en) * | 2001-03-14 | 2002-12-05 | Kuldipsingh Pabla | Method and apparatus for lightweight support on set top box |
US7350200B2 (en) * | 2001-03-29 | 2008-03-25 | Intel Corporation | Method and system of controlling dynamically compiled native code size |
US20040015862A1 (en) * | 2001-05-15 | 2004-01-22 | Dunn Jeffrey J. | Method and apparatus for automatic accessibility assessment |
US6799184B2 (en) | 2001-06-21 | 2004-09-28 | Sybase, Inc. | Relational database system providing XML query support |
US20040059866A1 (en) | 2001-06-25 | 2004-03-25 | Kayuri Patel | System and method for representing named data streams within an on-disk structure of a file system |
US20030093556A1 (en) | 2001-11-10 | 2003-05-15 | Toshiba Tec Kabushiki Kaisha | Document service appliance |
US6976241B2 (en) | 2001-11-14 | 2005-12-13 | Intel Corporation | Cross platform administrative framework |
US20030172368A1 (en) | 2001-12-26 | 2003-09-11 | Elizabeth Alumbaugh | System and method for autonomously generating heterogeneous data source interoperability bridges based on semantic modeling derived from self adapting ontology |
US20030151633A1 (en) | 2002-02-13 | 2003-08-14 | David George | Method and system for enabling connectivity to a data system |
US20040002942A1 (en) | 2002-06-28 | 2004-01-01 | Microsoft Corporation | System and method for managing file names for file system filter drivers |
US20040068480A1 (en) * | 2002-10-08 | 2004-04-08 | Lam Ioi K. | Method and apparatus for initializing romized system classes at virtual machine build time |
US20040078542A1 (en) * | 2002-10-14 | 2004-04-22 | Fuller William Tracy | Systems and methods for transparent expansion and management of online electronic storage |
US20040186857A1 (en) | 2003-03-18 | 2004-09-23 | Apple Computer Inc. | Localized viewing of file system names |
US20050015461A1 (en) | 2003-07-17 | 2005-01-20 | Bruno Richard | Distributed file system |
US20050060561A1 (en) * | 2003-07-31 | 2005-03-17 | Pearson Siani Lynne | Protection of data |
US20050038813A1 (en) | 2003-08-12 | 2005-02-17 | Vidur Apparao | System for incorporating information about a source and usage of a media asset into the asset itself |
US20050073982A1 (en) * | 2003-10-07 | 2005-04-07 | Accenture Global Services Gmbh. | Connector gateway |
US20050114381A1 (en) | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for generating extensible file system metadata |
US20050114363A1 (en) | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for detecting and storing file identity change information within a file system |
US20050114406A1 (en) * | 2003-11-26 | 2005-05-26 | Veritas Operating Corporation | System and method for detecting and storing file content access information within a file system |
US20060004759A1 (en) | 2004-06-07 | 2006-01-05 | Veritas Operating Corporation | System and method for file system content processing |
US20060004709A1 (en) | 2004-06-07 | 2006-01-05 | Veritas Operating Corporation | System and method for providing a programming-language-independent interface for querying file system content |
Non-Patent Citations (7)
Title |
---|
"DCMI Abstract Data Model," Dublin Core Metadata Initiative, Feb. 2004, downloaded from http://www.ukoln.ac.uk/metadata/dcmi/abstract-model/2004-02-04/, 17 pages. |
"Native XML Management With Documentum," Documentum Technical White Paper, Jul. 2003, downloaded from http://software.emc.com/collateral/content<SUB>-</SUB>management/documentum<SUB>-</SUB>family/wp<SUB>-</SUB>tech<SUB>-</SUB>xml.pdf, 15 pages. |
"The Business Rationale for Distributed (Remote) Document Capture," Verity White Paper, Oct. 2003, downloaded from http://www.cardiff.com/cms/groups/public/documents/collateral/mk0535.pdf, 12 pages. |
Autonomy Technology White Paper, Nov. 2003, downloaded from http://www.autonomy.com/content/downloads/White%20Papers/index.en.html, 19 pages. |
Autonomy XML White Paper, Oct. 2003, downloaded from http://www.autonomy.com/content/downloads/White%20Papers/index.en.html, 11 pages. |
Staples et al., "The Fedora Project: An Open-source Digital Object Repository Management System," in D-Lib Magazine, v. 9, No. 4, Apr. 2003, downloaded from http://web.archive.org/web/20040203065018/www.dlib.org/dlib/april03/staples/04staples.html, 12 pages. |
Wildermuth, "A Developer's Perspective on WinFS: Part 1," Mar. 2004, downloaded from http://web.archive.org/web/20050414063209/http://msdn.microsoft.com/data/winfs/default.aspx?pull=/library/en-us/dnwinfsta/html/winfsdevpersp.asp, 10 pages. |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080126374A1 (en) * | 2003-11-26 | 2008-05-29 | Dhrubajyoti Borthakur | System and method for detecting and storing file identity change information within a file system |
US7912866B2 (en) | 2003-11-26 | 2011-03-22 | Symantec Operating Corporation | System and method for detecting and storing file identity change information within a file system |
US11087071B2 (en) * | 2019-11-14 | 2021-08-10 | Ciena Corporation | Self-compressed YANG model |
Also Published As
Publication number | Publication date |
---|---|
US20050131955A1 (en) | 2005-06-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7653647B2 (en) | System and method for determining file system data integrity | |
US7487138B2 (en) | System and method for chunk-based indexing of file system content | |
US7272606B2 (en) | System and method for detecting and storing file content access information within a file system | |
US7657530B2 (en) | System and method for file system content processing | |
JP4944008B2 (en) | System, method and computer-accessible recording medium for searching efficient file contents in a file system | |
US7437375B2 (en) | System and method for communicating file system events using a publish-subscribe model | |
US6871245B2 (en) | File system translators and methods for implementing the same | |
US7562216B2 (en) | System and method for applying a file system security model to a query system | |
US20060059204A1 (en) | System and method for selectively indexing file system content | |
US7676526B1 (en) | System, method and computer program product for multi-level file-sharing by concurrent users | |
US7676481B2 (en) | Serialization of file system item(s) and associated entity(ies) | |
US7831552B2 (en) | System and method for querying file system content | |
US7415480B2 (en) | System and method for providing programming-language-independent access to file system content | |
WO2005055093A2 (en) | System and method for generating extensible file system metadata and file system content processing | |
US20060074912A1 (en) | System and method for determining file system content relevance | |
US8306991B2 (en) | System and method for providing a programming-language-independent interface for querying file system content | |
JP4279452B2 (en) | System and method for performing a predefined action when porting the namespace of one storage medium to the namespace of another storage medium | |
TW200408980A (en) | System and method for managing file names for file system filter drivers | |
US8332844B1 (en) | Root image caching and indexing for block-level distributed application management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VERITAS OPERATING CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BORTHAKUR, DHRUBAJYOTI;PREMO, NUR;REEL/FRAME:014810/0464 Effective date: 20031209 |
|
AS | Assignment |
Owner name: SYMANTEC CORPORATION, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:VERITAS OPERATING CORPORATION;REEL/FRAME:019872/0979 Effective date: 20061030 Owner name: SYMANTEC CORPORATION,CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:VERITAS OPERATING CORPORATION;REEL/FRAME:019872/0979 Effective date: 20061030 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: SYMANTEC OPERATING CORPORATION, CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED ON REEL 019872 FRAME 979. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNEE IS SYMANTEC OPERATING CORPORATION;ASSIGNOR:VERITAS OPERATING CORPORATION;REEL/FRAME:027819/0462 Effective date: 20061030 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: VERITAS US IP HOLDINGS LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SYMANTEC CORPORATION;REEL/FRAME:037697/0412 Effective date: 20160129 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0001 Effective date: 20160129 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CONNECTICUT Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0726 Effective date: 20160129 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0001 Effective date: 20160129 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATE Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0726 Effective date: 20160129 |
|
AS | Assignment |
Owner name: VERITAS TECHNOLOGIES LLC, CALIFORNIA Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:VERITAS US IP HOLDINGS LLC;VERITAS TECHNOLOGIES LLC;REEL/FRAME:038455/0752 Effective date: 20160329 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT, DELAWARE Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS TECHNOLOGIES LLC;REEL/FRAME:054370/0134 Effective date: 20200820 |
|
AS | Assignment |
Owner name: VERITAS US IP HOLDINGS, LLC, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:054535/0814 Effective date: 20201127 |