// wdm.h
CLFSUSER_API NTSTATUS ClfsAddLogContainer(
[in] PLOG_FILE_OBJECT plfoLog,
[in] PULONGLONG pcbContainer,
[in] PUNICODE_STRING puszContainerPath
);
View the official Windows Driver Kit DDI referenceNo description available.
The ClfsAddLogContainer routine adds a container to a CLFS log.
plfoLog [in]A pointer to a LOG_FILE_OBJECT structure that represents the log to which the container will be added. The caller previously obtained this pointer by calling ClfsCreateLogFile.
pcbContainer [in]A pointer to a ULONGLONG-typed variable. The role of this parameter depends on whether the log currently has at least one container.
puszContainerPath [in]A pointer to a UNICODE_STRING structure that supplies the path name for the new container. The path can be absolute or relative to the location of the base log file. Paths that are relative to the base log file must begin with CLFS_CONTAINER_RELATIVE_PREFIX, which is the string literal (L"%BLF%\").
ClfsAddLogContainer returns STATUS_SUCCESS if it succeeds; otherwise, it returns one of the error codes defined in Ntstatus.h.
A container is a contiguous extent on stable storage. For example, a container could be a contiguous file on disk. A log is a set of containers along with a base log file. For more information about containers, see CLFS Stable Storage.
A container specified by a path that is relative to the base log file must be in the same directory as the base log file or a subdirectory of the base log file. The directories "." and ".." are not allowed in a relative path.
A log can have some containers with absolute paths and other containers with relative paths.
Containers are created in a non-compressed mode and are initialized with zeros.
A log must have at least two containers before any I/O can be performed on it.
For an explanation of CLFS concepts and terminology, see Common Log File System.