search for: no_cow

Add the missing usage for No_COW since we''ve supported No_COW flag. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- misc/chattr.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/misc/chattr.c b/misc/chattr.c index 141ea6e..24254cc 100644 --- a/misc/chattr.c +++ b/misc/chattr.c @@ -83...

Add the missing usage for No_COW since we''ve supported No_COW flag. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- v1->v2: sort options alphabetically, thanks to Roman Mamedov. misc/chattr.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/misc/chattr.c b/misc/chattr.c index 141e...

...or empty files. If it is set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable. If the ''C'' flag is set on a directory, it will have no effect on the directory, but new files created in that directory will the No_COW attribute.) So what exactly does that mean? Does it mean that it is unsafe? Or does it mean that it is simply unreliable? If I run a btrfs balance first will that clear out the COW snapshots and enable me to perform the recursive chattrs? What is the best way to approach this? Thanks for a...