From: KC <conrad.francois.artus@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Options for SSD - autodefrag etc?
Date: Fri, 24 Jan 2014 19:55:58 +0100 [thread overview]
Message-ID: <52E2B73E.1050903@gmail.com> (raw)
>>> From: Duncan <1i5t5.duncan <at> cox.net>
>>> Subject: Re: Options for SSD - autodefrag etc?
>>> Newsgroups: gmane.comp.file-systems.btrfs
>>> Date: 2014-01-24 06:54:31 GMT (11 hours and 44 minutes ago)
>>> KC posted on Thu, 23 Jan 2014 23:23:35 +0100 as excerpted:
Duncan, thank you for this outstanding explanation. It was very
informative and helpful.
I only have one follow-up question.
I followed your advice on NOCOW for virtualbox images and torrents like so:
chattr -v /home/juha/VirtualBox\ VMs/
chattr -RC /home/juha/Downloads/torrent/#unfinished
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?
next reply other threads:[~2014-01-24 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 18:55 KC [this message]
2014-01-24 20:27 ` Options for SSD - autodefrag etc? Kai Krakow
2014-01-25 5:09 ` Duncan
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=52E2B73E.1050903@gmail.com \
--to=conrad.francois.artus@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.