linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: linux-btrfs@vger.kernel.org
Subject: How do I safely terminate COW on pre-existing files?
Date: Thu, 06 Jun 2013 19:51:28 -0700	[thread overview]
Message-ID: <51B14AB0.4040906@chinilu.com> (raw)

I want to eliminate the COW feature on all of my OS files.  It is a nice 
feature for user files, but I don't see a clear benefit for the actual 
OS files.  And I suspect that COW induced fragmentation is causing or 
aggravating problems with my system including the boot open_ctree 
problem.  I had planned to recursively chattr these files to "nodatacow" 
status but then I ran into this cryptic warning on the chattr man page:

(Note: For btrfs, the 'C' flag should be set on new 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 any tips,  George

             reply	other threads:[~2013-06-07  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07  2:51 George Mitchell [this message]
2013-06-07 11:52 ` How do I safely terminate COW on pre-existing files? David Sterba
2013-06-07 14:00   ` George Mitchell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51B14AB0.4040906@chinilu.com \
    --to=george@chinilu.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).