From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fossil disk usage over 100%?
Date: Mon, 3 Jun 2013 17:14:24 -0300 [thread overview]
Message-ID: <82B5F5A9-4D0B-4CBD-BE00-6C5A331B6E29@gmail.com> (raw)
In-Reply-To: <09fda244846e504aae2cdf208bb498c9@pi.att>
On Jun 3, 2013, at 4:50 PM, sl@9front.org wrote:
>>> Certainly. And we're back at square one. Everyone has their own story
>>> about how they lost data.
>>
>> which is to say that the thesis that fossil sucks is refuted.
>
> I think it rather says that everyone has a story. Someone was
> complaining about anecdotes, but that's what we've got.
>
> Richard mentioned fixing the snapshots bug in fossil. This
> is about as close as we've come to examining the technical
> issues.
>
> It's mostly been story/counter-story about how we all have
> lost files on each of these filesystems. The important takeaway
> here is that we have reports of people losing data on every single
> one of them.
>
> I had problems with fossil. Like you, I never had problems with
> (cw)fs. Charles had problems with fs. I don't think we've refuted
> any claims about relative stability or even established a scale
> to measure with.
>
> -sl
>
Awesome, I'm happy to know that there's no clear data about anything
and that everything can be proven wrong.
Don't worry, I'm not going to bore you with my stories about how fossil/venti
saved my life so many times and never lost a file, I'll just keep using it.
Thanks for sharing your wisdom with the list.
---
Federico G. Benavento
benavento@gmail.com
next prev parent reply other threads:[~2013-06-03 20:14 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 19:45 Jeremy Jackins
2013-05-30 20:47 ` Jeremy Jackins
2013-05-30 22:06 ` David du Colombier
2013-05-31 4:54 ` Jeremy Jackins
2013-05-31 5:20 ` lucio
2013-05-31 8:35 ` David du Colombier
2013-05-31 10:32 ` James Chapman
2013-05-31 10:34 ` James Chapman
2013-05-31 19:53 ` Steven Stallion
2013-05-31 20:06 ` Kurt H Maier
2013-06-01 3:43 ` Steven Stallion
2013-06-01 3:56 ` Matthew Veety
2013-06-01 6:09 ` Richard Miller
2013-06-01 7:29 ` steve
2013-06-01 12:39 ` Kurt H Maier
2013-06-02 15:55 ` Richard Miller
2013-06-02 15:59 ` Kurt H Maier
2013-06-02 16:09 ` lucio
2013-06-02 16:41 ` Skip Tavakkolian
2013-06-02 16:45 ` Matthew Veety
2013-06-02 16:49 ` Skip Tavakkolian
2013-06-02 16:53 ` Kurt H Maier
2013-06-02 17:01 ` Skip Tavakkolian
2013-06-02 17:13 ` Kurt H Maier
2013-06-02 17:29 ` Skip Tavakkolian
2013-06-02 21:58 ` hiro
2013-06-03 2:27 ` Skip Tavakkolian
2013-06-03 2:45 ` erik quanstrom
2013-06-03 10:55 ` Richard Miller
2013-06-03 11:49 ` Kurt H Maier
2013-06-03 12:05 ` lucio
2013-06-03 12:18 ` Richard Miller
2013-06-03 13:11 ` Charles Forsyth
2013-06-03 14:39 ` erik quanstrom
2013-06-03 15:45 ` sl
2013-06-03 19:27 ` Charles Forsyth
2013-06-03 19:32 ` sl
2013-06-03 19:41 ` erik quanstrom
2013-06-03 19:50 ` sl
2013-06-03 20:14 ` Federico G. Benavento [this message]
2013-06-03 20:20 ` sl
2013-06-03 22:17 ` Steve Simon
2013-06-03 23:10 ` Steven Stallion
2013-06-03 23:06 ` Steven Stallion
2013-06-04 4:37 ` Anthony Sorace
2013-06-04 4:46 ` sl
2013-06-04 9:23 ` Richard Miller
2013-06-03 20:21 ` Kurt H Maier
2013-06-03 19:36 ` Bakul Shah
2013-06-06 8:51 ` Aaron Sawyer
2013-06-02 21:20 ` hiro
2013-06-02 22:23 ` Charles Forsyth
2013-06-01 4:00 ` erik quanstrom
2013-06-04 4:51 sl
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=82B5F5A9-4D0B-4CBD-BE00-6C5A331B6E29@gmail.com \
--to=benavento@gmail.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).