A method includes determining a length of a file and storing the length of the file in a first memory location. An endpoint of a last complete record within the file is determined and the endpoint is stored in a second memory location. The length of the file stored in the first memory location is compared to a current length of the file, and a data structure associated with the file is updated beginning at the endpoint if the current length of the file exceeds the length of the file stored in the first memory location.

In a hierarchical storage memory (HSM), a file recalled by a specific application is migrated as soon as possible after completion of the application process. Specifically, the effective UID of a specific process is preregistered on an HSM client. After a recall operation is performed on a certain file from the user ID, when there is no access from the UID to the file for a given length of time, the file is migrated. This prevents files premigrated by access from any application other than the specific one from being handled in the same way, resolving a disadvantageous problem caused when these (premigrated) files are not desired to be migrated preferentially.

An apparatus includes a processor component of a first node device caused to receive data block encryption data and an indication of size of an encrypted data block distributed to the first node device for decryption, and in response to the data set being of encrypted data: receive an indication of the quantity of sub-blocks within the encrypted data block, and a hashed identifier for each data sub-block; use the data block encryption data to decrypt the encrypted data block to regenerate data set portions from the data sub-blocks; analyze the hashed identifier of each data sub-block to determine whether all data set portions are distributed to the first node device for processing; and in response to a determination that at least one data set portion is to be distributed to a second node device for processing, transmit the at least one data set portion to the second node device.

In file storage, a CPU is configured to: divide a file into a plurality of chunks, execute encoding processing on at least one of the chunks to obtain an encoded chunk, and store in cloud storage a plurality of chunks of the file including the encoded chunk; acquire, when receiving a read command of which target is data of a part of a file stored in the cloud storage, a read target chunk including data, which is a target of the read command, from the cloud storage; and execute, when an encoded chunk is included in the read target chunk, decoding processing on the encoded chunk, identify data that is a read target from the read target chunk including the chunk having been subjected to decoding processing, and hand over the identified data to a command source of the read command.

Preventing applications from overconsuming shared storage resources, including: identifying one or more sub-regions of data stored on a storage device that are associated with an application of a known application type; compiling information describing the application's utilization of a storage system; determining that a storage system objective has not been met; and initiating, based on the information describing the application's utilization of the storage system, remediation actions.

Systems and methods for file management by mobile computing devices. An example method, performed by a computer system, may comprise: storing, by a computer system, a first file having a first size, in a memory; storing, in the memory, a second file derived from the first file, the second file having the second size, the second size being less than the first size; determining that the memory is not sufficient to perform a memory write operation; selecting a third file having a fourth file associated with it, the fourth file derived from the third file; and removing the third file from the memory.

Techniques described herein relate to systems and methods of data storage, and more particularly to providing layering of file system functionality on an object interface. In certain embodiments, file system functionality may be layered on cloud object interfaces to provide cloud-based storage while allowing for functionality expected from a legacy applications. For instance, POSIX interfaces and semantics may be layered on cloud-based storage, while providing access to data in a manner consistent with file-based access with data organization in name hierarchies. Various embodiments also may provide for memory mapping of data so that memory map changes are reflected in persistent storage while ensuring consistency between memory map changes and writes. For example, by transforming a ZFS file system disk-based storage into ZFS cloud-based storage, the ZFS file system gains the elastic nature of cloud storage.

Generating a storage interface includes receiving a request for documents, detecting an accounting workflow type corresponding to request, and identifying a document organizational structure matching the accounting workflow type. Further, a virtual storage interface is built using an index on the documents and according to the document organizational structure, and presented.

A storage method includes determining layers that are to be merged in a database; determining a data block that is to be modified based on files of the layers that are to be merged in the database; reading a corresponding data block in the memory and reorganizing the read data block, according to a key corresponding to the data block that is to be modified; replacing the data block that is to be modified in the memory with the reorganized data block, when byte size of the reorganized data block does not exceed a first preset value; and storing the key and statistical information of the reorganized data block in a corresponding file of the database.

Methods and devices are provided in which a controller of a storage device receives a read command including at least a file pointer of a file, from an application at a host device. The controller retrieves a physical block address (PBA) list associated with file data from a table maintained at the controller using the file pointer. The controller reads data from a memory using the PBA list, and provides the file data to the application at the host device.