linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Glatt <mail@hachre.de>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
	Duncan <1i5t5.duncan@cox.net>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Recommended settings for SSD
Date: Sun, 26 May 2013 17:16:10 +0200	[thread overview]
Message-ID: <CAFWF=akw41MyFLAasCx90M6MU7dBU8DVEMDzRMsiEwNMFZMkOA@mail.gmail.com> (raw)
In-Reply-To: <CAAeznTr8t+AnTL9JtXLA+TMg97_MX+63giGEsrP-j4rWFUhYpg@mail.gmail.com>

I don't know a better way to check than doing df -h before and
after... If you use space_cache you have to clear_cache though to make
the numbers be current for sure each time before looking at df.

Old kernel can be a problem. You can use the Arch CDs to do it, they
usually come with the newest kernels.
https://www.archlinux.org/download/

If you need to install anything a quick guide to the package managing:

# Update Repos and Upgrade system:
pacman -Suy

# Install a specific package:
pacman -S packagename

# Search for a package
pacman -Ss search term


On Sun, May 26, 2013 at 12:00 PM, Leonidas Spyropoulos
<artafinde@gmail.com> wrote:
> On Sat, May 25, 2013 at 11:33 PM, Harald Glatt <mail@hachre.de> wrote:
>> Data that already exists will only be compressed on re-write. You can
>> do it with btrfs fi defrag and a script that traverses the fs to call
>> defrag on every file. Another good way is the find command that has
>> been outlined here:
>>
>> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Defragmenting_a_directory_doesn.27t_work
>>
>
> I tried to my home partition the 'find' command and worked without
> errors, not sure if it did compress (how can I check?). I tried also
> on the root partition and every file that was in use (obviously) it
> didn't defrag it. I am guessing I have to mount the partition from a
> LiveCD but since the LiceCD kernel is usually old (in terms of btrfs)
> do you reckon there will be any problems?
>
> Thanks
> --
> Caution: breathing may be hazardous to your health.
>
> #include <stdio.h>
> int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");}

  reply	other threads:[~2013-05-26 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 20:06 Recommended settings for SSD Leonidas Spyropoulos
2013-05-24 20:07 ` cwillu
2013-05-24 22:38   ` Leonidas Spyropoulos
2013-05-25  3:58     ` Duncan
2013-05-25  8:21       ` Leonidas Spyropoulos
2013-05-25 10:14         ` Russell Coker
2013-05-25 12:13       ` Martin Steigerwald
2013-05-25 13:30         ` Duncan
2013-05-25 22:29         ` Leonidas Spyropoulos
2013-05-25 22:33           ` Harald Glatt
2013-05-26 10:00             ` Leonidas Spyropoulos
2013-05-26 15:16               ` Harald Glatt [this message]
2013-05-26 17:06                 ` cwillu
2013-05-25 22:49           ` Martin Steigerwald
2013-05-25 22:46         ` 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='CAFWF=akw41MyFLAasCx90M6MU7dBU8DVEMDzRMsiEwNMFZMkOA@mail.gmail.com' \
    --to=mail@hachre.de \
    --cc=1i5t5.duncan@cox.net \
    --cc=Martin@lichtvoll.de \
    --cc=artafinde@gmail.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).