9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is fossil/venti file system a good choice for SSD?
Date: Sun,  4 Feb 2018 15:46:14 -0800	[thread overview]
Message-ID: <20180204234629.C6033156E812@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 04 Feb 2018 11:02:57 +0100." <CAFSF3XNWyzh3WFergj5frBsBv9=nkC6=BeuL6=8_36yr3F0yfQ@mail.gmail.com>

On Sun, 04 Feb 2018 11:02:57 +0100 hiro <23hiro@gmail.com> wrote:
hiro writes:
> For home use a ZFS intent log and caches on a good 2,5" SSD in a
> battery-backed thinkpad seems like an easy, silent, fast and stable
> (even against data loss from power outage) basis, even if you only
> connect shitty USB3 HDD drives externally for the pools. Your data
> should be safe on the SSD as long as you make sure it's
> underprovisioned enough to make fair use of wear leveling for a long
> time.

Many of these USB3 HDDs have 1 year warranty for a reason.
SMART check on a few month old Seagate USB3 disk I have shows
it has already exceeded worst case of many parameters! It
still works so I can't return it.

You can buy 5 year warranty WD Gold or RE for decent prizes
and can put together your own disk array.

I don't use a separate ZFS intent log on my main fileserver as
I don't rely on NFS much (mostly just readonly access).  I
also don't use a laptops for fileservice as they don't have
ECC memory.



  reply	other threads:[~2018-02-04 23:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03  9:39 lchg
2018-02-03 10:54 ` Ethan Grammatikidis
2018-02-03 12:45 ` Steve Simon
2018-02-03 13:25   ` hiro
2018-02-03 14:53     ` Steve Simon
2018-02-03 16:53       ` hiro
2018-02-03 18:49         ` Digby R.S. Tarvin
2018-02-03 20:10           ` Bakul Shah
2018-02-03 21:46             ` Digby R.S. Tarvin
2018-02-03 23:46               ` Bakul Shah
2018-02-04  9:45                 ` [9fans] RasPi why? Ethan Grammatikidis
2018-02-04 15:05                   ` Rui Carmo
2018-02-04 16:36                   ` Steve Simon
2018-02-04 21:00                   ` Lyndon Nerenberg
2018-02-04 21:55                   ` Bakul Shah
2018-02-04 22:23                     ` hiro
2018-02-04 23:46                   ` Skip Tavakkolian
2018-02-04 23:52                     ` Lyndon Nerenberg
2018-02-05  9:22                     ` hiro
2018-02-05  9:27                       ` Rui Carmo
2018-02-05  9:48                         ` hiro
2018-02-05  9:49                           ` hiro
2018-02-04 10:02                 ` [9fans] Is fossil/venti file system a good choice for SSD? hiro
2018-02-04 23:46                   ` Bakul Shah [this message]
2018-02-05  8:50                     ` hiro
2018-02-04  9:52               ` hiro
2018-02-04 16:15                 ` Digby R.S. Tarvin
2018-02-04 21:46                   ` hiro
2018-02-04 22:47                     ` Digby R.S. Tarvin
2018-02-05  9:54                       ` hiro
2018-02-04  9:49           ` hiro
2018-02-04 22:22 ` Ole-Hjalmar Kristensen

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=20180204234629.C6033156E812@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).