Abstract: A storage stack delete notification can be received at a storage stack filter. The delete notification can indicate deletion of primary data in a primary storage region. Secondary data that is taking up storage resources managed by the storage stack filter can be identified. The secondary data can be associated with the primary storage region, and the storage resources can be resources other than the primary storage region. It can be determined whether it is useful to have the secondary data continue taking up the storage resources. If having the secondary data continue taking up the storage resources is not useful, then the storage resources can be freed.

Abstract: Embodiments include a file system data structure and file system recognition APIs that may allow an operating system to identify a partition of a storage device as having a valid file system, even if the operating system does not know how to access the file system a priori. File systems can implement these data structures in a standardized, known location within a partition on the storage device such that an operating system may use APIs or other functions to examine the known location for the presence of these data structures. Information on how to interpret the data structure may be obtained using a network or other source.

Abstract: An application programming interface (API) module provides access to data, independent of filesystem implementation in a non-privileged user mode. A discovery volume having a filesystem recognizable by an operating system has cover files which prevent damage to data stored in an unrecognizable primary volume. The discovery volume also includes a data access API available for execution in a non-privileged user mode to render the primary volume accessible by operating systems which would otherwise find the primary volume unrecognizable.

Abstract: A delete notification can be received at a storage stack filter in a storage stack. It can be determined whether the delete notification applies to an entire storage volume. If the delete notification does not apply to the entire storage volume, a first set of actions can be taken with the storage stack filter in response to the delete notification. If the delete notification does apply to the entire storage volume, a second set of actions can be taken with the storage stack filter in response to the delete notification.

Abstract: A file system which is enabled to use a Metadata Partition instead of VAT for write-once discs, is provided by a pseudo-overwrite method. On applying this invention to a drive apparatus which supports pseudo-overwrite media, the file system distinguishes data to overwrite from data to append. When the data is newly written to a logical sector, the drive apparatus writes the data to a physical sector to which the logical sector corresponds. When the logical sector is overwritten the data is written to another unrecorded physical sector in the volume space, and remapping information that specifies the original address, and the remapping address are stored in the remapping table.

Abstract: Aspects of the subject matter described herein relate to file system filters and transactions. In aspects, a filter may enlist to receive notification of events associated with a transaction. Afterwards, the filter may receive notification of a transaction event for which it has enlisted. In response to receiving notification of the transaction the filter may perform an action as appropriate. Aspects of the subject matter described herein may be applied to stacked and managed filters.

Abstract: A file system is enabled to use a Metadata Partition instead of VAT for write-once discs, and is provided by a pseudo-overwrite method with a plurality of tracks especially for metadata and file data. On applying this invention to a drive apparatus that supports pseudo-overwrite media, the file system distinguishes data to overwrite from data to append (S1701). When the data is newly written to a logical sector, the drive apparatus writes the data to a physical sector to which the logical sector corresponds (S1703). When the data being overwritten is data stored in the logical sector, the data is written to the other unrecorded physical sector in the volume space (S1704), and remapping information is written (S1705). The remapping information specifies the original address of the physical sector, and the remapping address of the physical sector in which the data is written.

Abstract: An application programming interface (API) module provides access to data, independent of filesystem implementation in a non-privileged user mode. A discovery volume having a filesystem recognizable by an operating system has cover files which prevent damage to data stored in an unrecognizable primary volume. The discovery volume also includes a data access API available for execution in a non-privileged user mode to render the primary volume accessible by operating systems which would otherwise find the primary volume unrecognizable.

Abstract: An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated.

Abstract: An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated.

Abstract: An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated.

Abstract: Aspects of the subject matter described herein relate to file system filters and transactions. In aspects, a filter may enlist to receive notification of events associated with a transaction. Afterwards, the filter may receive notification of a transaction event for which it has enlisted. In response to receiving notification of the transaction the filter may perform an action as appropriate. Aspects of the subject matter described herein may be applied to stacked and managed filters.

Abstract: An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated.

Abstract: A set of file system data structure and file system recognition APIs are disclosed that may allow an operating system to identify a partition of a storage device as having a valid file system, even if the operating system does not know how to access the file system a priori. File systems implement these data structures in a standardized, known location within a partition on the storage device such that an operating system may use APIs or other functions to examine that known location for the presence of these data structures. Information on how to interpret the data structure may be obtained using a network or other source.

Abstract: In accordance with one or more aspects, one or more portions of each of multiple files that have been freed are determined. One or more delete notifications are generated identifying the one or more portions of the multiple files. Each portion is identified as a range of data on a storage device, and each delete notification includes one or more ranges of data on the storage device. These generated delete notifications are then sent to a storage stack. Additionally, an application can determine that one or more ranges of data of a storage device are to be freed and send a delete notification, in the absence of a file system on the device, to the storage stack identifying the one or more ranges of data of the storage device that are to be freed.

Abstract: A recording method of the present invention includes the steps of: receiving a write instruction which specifies at least a logical sector in which data is to be written; determining whether the logical sector specified by the write instruction corresponds to a recorded physical sector or an unrecorded physical sector (S1111); when it is determined that the logical sector specified by the write instruction corresponds to an unrecorded physical sector, writing the data into the unrecorded physical sector (S1112); and when it is determined that the logical sector specified by the write instruction corresponds to a recorded physical sector, writing the data into an unrecorded physical sector other than the recorded physical sector (S1113), generating a remapping table including remapping information which remaps an original address of the recorded physical sector to a remapping address of the selected physical sector, and writing the remapping table on the write-once disc (S1114).

Abstract: The recording method of the present invention includes the steps of: receiving a write instruction which specifies at least a logical sector in which data is to be written; determining whether the logical sector corresponds to a recorded physical sector or an unrecorded physical sector; when it is determined that the logical sector corresponds to an unrecorded physical sector, writing the data into the unrecorded physical sector, determining whether a verification of the data which has been written into a physical sector is successful, if the verification of the data that has been written is not successful, writing the data into an unrecorded physical sector, generating a remapping table including remapping information which remaps an original address of the physical sector corresponding to the logical sector to a remapping address of the selected physical sector, and writing the remapping table on the write-once disc.

Abstract: An application programming interface (API) module provides access to data, independent of filesystem implementation in a non-privileged user mode. A discovery volume having a filesystem recognizable by an operating system has cover files which prevent damage to data stored in an unrecognizable primary volume. The discovery volume also includes a data access API available for execution in a non-privileged user mode to render the primary volume accessible by operating systems which would otherwise find the primary volume unrecognizable.

Abstract: A storage stack delete notification can be received at a storage stack filter. The delete notification can indicate deletion of primary data in a primary storage region. Secondary data that is taking up storage resources managed by the storage stack filter can be identified. The secondary data can be associated with the primary storage region, and the storage resources can be resources other than the primary storage region. It can be determined whether it is useful to have the secondary data continue taking up the storage resources. If having the secondary data continue taking up the storage resources is not useful, then the storage resources can be freed.

Abstract: A delete notification can be received at a storage stack filter in a storage stack. It can be determined whether the delete notification applies to an entire storage volume. If the delete notification does not apply to the entire storage volume, a first set of actions can be taken with the storage stack filter in response to the delete notification. If the delete notification does apply to the entire storage volume, a second set of actions can be taken with the storage stack filter in response to the delete notification.