linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Options for SSD - autodefrag etc?
Date: Sat, 25 Jan 2014 05:09:35 +0000 (UTC)	[thread overview]
Message-ID: <pan$a07a$608e1613$631e8f4f$ff0dfe6@cox.net> (raw)
In-Reply-To: 7uuara-hf5.ln1@hurikhan77.spdns.de

Kai Krakow posted on Fri, 24 Jan 2014 21:27:19 +0100 as excerpted:

> KC <conrad.francois.artus@googlemail.com> schrieb:
> 
>> I followed your advice on NOCOW for virtualbox images and torrents
>> [...]
>> 
>> As you can see, i used the recursive flag. However, I do not know
>> whether this will automatically apply to files that will be created in
>> the future in subfolders that do not yet exist.
>> 
>> Also, how can I confirm whether a file/folder has a NOCOW attribute set
>> on it?
> 
> The C attribute is also inherited by newly created directories. But keep
> in mind that, at the time applied, it only has effects on existing files
> if they are empty (read: never written to yet). Newly created files will
> inherit the attribute from its directory and then behave as expected.
> 
> You can use lsattr to confirm the C attribute was set. But again keep in
> mind: it does not reflect the file is actually nocow because of the
> above caveat.

Excellent reply (including what I snipped).  I don't actually work with 
VMs or other huge internal-write files much here, and don't otherwise 
work with extended attributes much, so would have had to lookup lsattr, 
and wasn't actually sure on the nested subdirs inheritance point myself 
tho I thought it /should/ work that way.

And your chattr/rsync routine ensures all data will be newly copied in 
AFTER the chattr on the dir, thus nicely addressing the very critical 
point about NEW DATA ONLY coverage I was most worried about communicating 
correctly. =:^)

Which is why I so enjoy mailing lists and newsgroups.  Time and again 
I've seen one person's answer simply not getting the whole job done no 
matter how mightily they struggle to do so, but because it's a public 
list/group, someone else steps in with a followup that addresses the gaps 
left by the first answer.  It nicely takes the pressure off any one 
person to have the "perfect" reply "every" time, as well as benefiting 
untold numbers of lurkers who now understand something they didn't know 
before, but may have never thought to ask themselves. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-01-25  5:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 18:55 Options for SSD - autodefrag etc? KC
2014-01-24 20:27 ` Kai Krakow
2014-01-25  5:09   ` Duncan [this message]
2014-01-25 13:33   ` Imran Geriskovan
2014-01-25 14:01     ` Martin Steigerwald
2014-01-26 17:18       ` Duncan
     [not found]         ` <KA9w1n01A0tVtje01A9yLn>
2014-01-28 11:41           ` Duncan
  -- strict thread matches above, loose matches on Subject: below --
2014-01-23 22:23 KC
2014-01-24  6:54 ` Duncan
2014-01-25 12:54   ` Martin Steigerwald
2014-01-26 21:44     ` Duncan
2014-01-24 20:14 ` Kai Krakow
2014-01-25 13:11   ` Martin Steigerwald
2014-01-25 14:06     ` Kai Krakow
2014-01-25 16:19       ` Martin Steigerwald

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='pan$a07a$608e1613$631e8f4f$ff0dfe6@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).