Stacked file systems and methods
AssigneeHewlett-Packard Development Company, L.P.
InventorsJaroslav Delapedraja, Mike Wenzel
Life of this patent
Estimating the term…
Abstract
Embodiments of a stacked file system and method are disclosed. One system embodiment includes a memory including a stack that includes a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module; and logic configured to create a stack template comprising information about the stack.
Claims50
A stacked file system, comprising:
- a memory including a stack that includes a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module;
- logic configured to validate the stack before the stack is created, based at least in part on a stack template, the stack template including a description of the first and second modules of the stack,
- wherein the logic is to validate a base file system constraint of the stack when the stack is mounted and
- wherein the stack template further includes at least one of a version string, a constraint on a base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template;
- and
- second logic to mount the validated stack to the base file system.
A stacked file method, comprising:
- providing a text file corresponding to a stack that includes a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module, the text file listing the first module and the second module;
- validating the stack before mounting the stack;
- providing a stack template comprising information about the validated stack;
- validating a base file system constraint of the stack;
- and
- mounting the validated stack to a base file system, wherein the stack template further includes at least one of a version string, a constraint on the base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template.
A stacked file system, comprising:
- means for storing a stack comprising a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module, wherein the means for storing includes at least one of a memory and a disk;
- means for validating the stack before mounting the stack;
- means for creating a stack template comprising information about the validated stack;
- means for validating a base file system constraint of the stack;
- and
- means for mounting the validated stack to at least one of a base file system and a second stack template, wherein the stack template further includes at least one of a version string, a constraint on a base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template.
A tangible computer readable medium storing machine executable instructions, which, when executed, cause a machine to at least:
- logic to create a text file which lists a first module and a second module that are in a stack, the first module including executable code that has distinct functionality from executable code of the second module;
- logic to create a stack template comprising stack information;
- logic to validate a base file system constraint of the stack;
- logic to validate the stack before the stack is created based on the stack information:
- and
- logic to mount the validated stack to the base file system, wherein the stack template further includes at least one of a version string, a constraint on a base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template.
A computer, comprising;
- a memory including a stack that includes a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module;
- an operating system comprising create logic to create a stack template comprising information about the stack, validate logic to validate the stack before a mounting operation and to validate a base file system constraint of the stack, and mount logic to mount the validated stack;
- and
- a processor to execute the logic and the executable code, wherein the stack template further includes at least one of a version string, a constraint on a base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template.
A stacked file system, comprising:
- a memory including a stack that includes a first module and a second module, the first module including executable code that has distinct functionality from executable code of the second module;
- logic to determine if the stack is valid before the stack is created, and if so, to create the validated stack and a stack template comprising information about the validated stack and to validate a base file system constraint of the stack;
- and
- second logic to mount the validated stack to the base file system, wherein the stack template further includes at least one of a version string, a constraint on a base file system to be used with the stack template, a file system type of the first module and the second module, mount option strings for the first module and the second module, and a list of base file systems to be excluded in a mount operation corresponding to the stack template.
Dependencies are inferred from the claim text.