Details
-
New Feature
-
Resolution: Won't Fix
-
Minor
-
None
-
Lustre 2.6.0
-
9223372036854775807
Description
DL-SNAP is a feature designed for directory level file backups.
It is implemented on top of lustre ldiskfs without modification of ext4 disk format, though we set a special original flag to FEATURE of the superblock in order to check whether DL-SNAP is enabled.
The feature makes execution of e2fsck command failed although no modification to ext2 file system structure.
DL-SNAP uses COW(Copy On Write) mechanism to reduce backup time and storage usage. When we create a snapshot, only inodes are created. At this point, new data blocks are not allocated on OST. Data blocks of snapshot are allocated when original file is modified.
Not only root users but also ordinary users can create snapshots. Users can create a snapshot of a directory using lfs command with snapshot option, and restore files by usual process such as cp command.
For more information, please check the presentation at LUG2016.
We didn't understand that adding original code to ldiskfs is not acceptable, because there are some patches(lustre/kernel_patches/patches/) modifying original kernel source.
This DL-SNAP code is impossible to be merged into Ext4 mainline and it is impossible to realize DL-SNAP feature without adding code to ldiskfs.
So we think it is impossible to be merged into lustre.
For future reference, could you tell us the rules(which sources are acceptable or not to modify), difference in contents or polices of "ldiskfs/kernel_patches/patches/" and "lustre/kernel_patches/patches/".
For example, can we create patches(not merged in mainline) which modify kernel code in "lustre/kernel_patches/patches/"?