From: Pavel Volkov <sailor@lists.xtsubasa.org>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: Using BTRFS on SSD now ?
Date: Sun, 08 Jun 2014 18:26:38 +0400 [thread overview]
Message-ID: <235dd10c-2595-4778-b6cb-6a2aa8bed686@lists.xtsubasa.org> (raw)
In-Reply-To: <20140605211144.5541fe9c@natsu>
On Thursday, June 5, 2014 7:11:44 PM MSK, Roman Mamedov wrote:
> Yeah, a PSA of sorts: take whatever SSDs you have and use, and go to the
> manufacturer's website (right *NOW* :) to check if they have a
> newer firmware,
> or to ensure that you have the latest version. There are such horrible
bugs
> being found and fixed in those, that upgrading the firmware is
> absolutely *not*
> the case of "if it's not broken, don't fix it". Also your SSD
> may gain niceties
> such as a working TRIM support (that was sometimes
> disabled/broken in earlier
> releases).
>
Sometimes the latest firmware has isuues which were not present earlier
(like in my case with Crucial M4) so we have to be careful and listen to
other users,
Maybe M4 is ok now, I'll have to check again,
next prev parent reply other threads:[~2014-06-08 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:30 Using BTRFS on SSD now ? Swâmi Petaramesh
2014-06-05 14:42 ` Russell Coker
2014-06-05 15:14 ` Swâmi Petaramesh
2014-06-05 16:26 ` Marc MERLIN
2014-06-05 18:34 ` Chris Murphy
2014-06-05 14:56 ` Marc MERLIN
2014-06-05 15:11 ` Roman Mamedov
2014-06-08 14:26 ` Pavel Volkov [this message]
2014-06-05 15:59 ` Christoph Anton Mitterer
2014-06-05 17:07 ` Swâmi Petaramesh
2014-06-05 18:13 ` Chris Murphy
2014-06-05 19:05 ` Marc MERLIN
2014-06-05 22:25 ` Duncan
2014-06-05 23:58 ` Martin K. Petersen
2014-06-06 0:24 ` Chris Murphy
2014-06-06 0:35 ` Duncan
2014-06-08 14:48 ` Pavel Volkov
2014-06-08 16:51 ` Martin K. Petersen
2014-06-05 21:15 ` Duncan
2014-06-05 16:17 ` Martin Steigerwald
2014-06-05 18:00 ` Chris Murphy
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=235dd10c-2595-4778-b6cb-6a2aa8bed686@lists.xtsubasa.org \
--to=sailor@lists.xtsubasa.org \
--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.