Techniques for efficient file operations

A system that performs a file operation on an inputted file on a computer system, comprising:

• a data store;
• at least one processor;
• and
• memory that comprises computer-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform acts including:
• writing file data from the inputted file to a first location in the data store;
• creating a first file name that points to the file data, wherein the first file name is a hard link to the file data and is retained in a second location in the data store;
• subsequent to the file data being written to the first location in the data store and as part of one of installation or removal of the inputted file, causing the file data retained at the first location in the data store to be continuously locked until termination of the installation or the removal of the inputted file, wherein the file data is immutable when locked;
• and
• while the file data is continuously locked at the first location in the data store during the installation or the removal of the inputted file:
• verifying the file data as locked at the first location in the data store, wherein the file data as locked at the first location in the data store is verified by detecting presence or absence of an error in the file data;
• receiving a file operation command related to the file data;
• and
• performing the file operation command while the file data remains locked during the installation or the removal of the inputted file, wherein the file operation command is one of a move command or a copy command.

A computer-readable storage medium including computer-executable instructions that, when executed by a processor, cause the processor to perform acts including:

• writing file data from an inputted file to a first location in a data store;
• creating a first file name retained at a second location in the data store, wherein the first file name is a hard link to the file data;
• subsequent to the file data being written to the first location in the data store and as part of installation of the inputted file, causing the file data retained at the first location in the data store to be continuously locked until termination of the installation of the inputted file;
• and
• while the file data is continuously locked at the first location in the data store during the installation of the inputted file:
• verifying the file data as locked at the first location in the data store by detecting presence or absence of an error in the file data;
• caching verification result information generated from the verifying of the file data, the verification result information being cached so long as the file data remains locked and discarded when the file data is unlocked;
• receiving a file operation command related to the file data during the installation of the inputted file;
• and
• creating a second file name retained at a third location in the data store in response to the file operation command while the file data remains locked at the first location in the data store, wherein the second file name is a hard link to the file data.