From: Martin Steigerwald <Martin@lichtvoll.de>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: 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 00:49:18 +0200 [thread overview]
Message-ID: <1678992.ZSqdH6UUdd@merkaba> (raw)
In-Reply-To: <CAAeznTq_+fv5SoPcr7ZYmYAvora2VCgN1WR9c8q=jPHNZORYrw@mail.gmail.com>
Am Samstag, 25. Mai 2013, 23:29:41 schrieb Leonidas Spyropoulos:
> On Sat, May 25, 2013 at 1:13 PM, Martin Steigerwald <Martin@lichtvoll.de> wrote:
> > Am Samstag, 25. Mai 2013, 03:58:12 schrieb Duncan:
> > [...]
> > And can be verified by:
> >
> > martin@merkaba:~> grep ssd /proc/mounts
> > /dev/mapper/merkaba-debian / btrfs rw,noatime,compress=lzo,ssd,space_cache 0 0
> > /dev/mapper/merkaba-debian /mnt/debian-zeit btrfs
> > rw,noatime,compress=lzo,ssd,space_cache 0 0
> > /dev/mapper/merkaba-home /home btrfs rw,noatime,compress=lzo,ssd,space_cache 0
> > 0
> > /dev/mapper/merkaba-home /mnt/home-zeit btrfs
> > rw,noatime,compress=lzo,ssd,space_cache 0 0
> > martin@merkaba:~> grep ssd /etc/fstab
> > martin@merkaba:~#1>
> > [...]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I see you are using compression. I don't have compression at the
> moment and I would like to use it. What will happen to the data that
> are already on the partitions? Will it be compressed when I use them?
> Do I have to re-write them? Would it be compressed with btrfs defrag
> command?
>
> Thanks for the information
Only new or defragmented data as Harald explained already.
Beware: I wouldn´t use compression on SSDs that compress themselves, like
any modern SandForce SSDs I bet.
The Intel SSD 320 in use here doesn´t compress itself, it just encrypts.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-05-25 22:49 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
2013-05-26 17:06 ` cwillu
2013-05-25 22:49 ` Martin Steigerwald [this message]
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=1678992.ZSqdH6UUdd@merkaba \
--to=martin@lichtvoll.de \
--cc=1i5t5.duncan@cox.net \
--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 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.