From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] experience thus far
Date: Sat, 17 May 2014 08:08:17 +0800 [thread overview]
Message-ID: <5376A871.7010609@iinet.net.au> (raw)
In-Reply-To: <20140516221558.19e69a5b@marcec>
On 17/05/14 04:15, Marc Joliet wrote:
> So, a week has passed since my conversion to btrfs.
>
> So far there seem to have been no problems, my system has been running as if
> nothing has changed :) . Which, as a friend pointed out, is how it should be.
>
> I don't think there is anything particularly interesting to mention in addition
> to what I already wrote. I can just say that I think the effort was worth it.
>
> The one thing that I can tell from reading the past two weeks of the btrfs ML
> is that the 3.15 Linux kernel series will contain lots of bug fixes (for
> example in balancing, error handling, and send/receive), and that I will want
> to use that sooner rather than later. Of course, the severity of the problems
> varies, and a lot are triggered under odd, or at least uncommon, circumstances.
> Still, its worth paying attention to.
>
> Also, a lot of problem reports I saw came from people using other volume
> management below btrfs, interestingly enough.
>
> As for the future, I think I will wait a while, and get some experience with
> btrfs first. I suspect that by the time btrfs supports swap files, it will be
> stable enough that I would consider converting my SSD to also use btrfs
> anyway :) . Possibly before that, once I am fully convinced of btrfs'
> stability, I will also convert my backup drive and switch to using snapshots
> and send/receive to perform backups. Perhaps somebody will have written a
> backup solution on top of snapshots by then.
>
> Have a nice weekend,
>
Don't forget to have a maintenance program - run a scrub regularly once
a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens
att) to see about one or two scrub fixable errors a week with no obvious
cause, sometimes serious (in a critical file). My experience is that if
you ignore these errors they seem to increase over time resulting in a
crash and burn. Keep an eye on your logs as btrfs will list the errors
there as well ("grep -i btrfs /var/log/messages"). For the ones scrub
cant fix, delete the file and restore from backup. Errors that require
off-line fixing (btrfsck) are the ones where I have lost file systems -
though I have not seen this in the last 6 months.
I am quite practised in restoring from backups because of btrfs :)
BillK
next prev parent reply other threads:[~2014-05-17 0:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:18 [gentoo-user] planned btrfs conversion: questions Marc Joliet
2014-05-06 18:13 ` [gentoo-user] " James
2014-05-06 23:30 ` Marc Joliet
2014-05-06 22:53 ` [gentoo-user] " Marc Joliet
2014-05-07 15:12 ` Marc Joliet
2014-05-09 21:05 ` Marc Joliet
2014-05-06 22:56 ` William Kenworthy
2014-05-06 23:51 ` Marc Joliet
2014-05-08 11:57 ` William Kenworthy
2014-05-08 18:14 ` Stefan G. Weichinger
2014-05-09 19:59 ` Stefan G. Weichinger
2014-05-10 11:14 ` Stefan G. Weichinger
2014-05-11 12:35 ` Stefan G. Weichinger
2014-05-11 16:17 ` Stefan G. Weichinger
2014-05-11 17:37 ` Peter Humphrey
2014-05-11 21:24 ` [gentoo-user] btrfs conversion: first impressions Stefan G. Weichinger
2014-05-12 14:30 ` Marc Joliet
2014-05-12 18:28 ` Stefan G. Weichinger
2014-05-13 22:34 ` Stefan G. Weichinger
2014-05-13 23:02 ` Neil Bothwick
2014-05-13 23:09 ` Stefan G. Weichinger
2014-05-14 0:39 ` Neil Bothwick
2014-05-14 8:01 ` Stefan G. Weichinger
2014-05-14 8:42 ` Neil Bothwick
2014-05-14 8:54 ` Stefan G. Weichinger
2014-05-14 9:26 ` Neil Bothwick
2014-05-14 9:30 ` Stefan G. Weichinger
2014-05-15 6:17 ` Stefan G. Weichinger
2014-05-12 11:19 ` [gentoo-user] planned btrfs conversion: questions Stefan G. Weichinger
2014-05-08 20:43 ` Marc Joliet
2014-05-10 9:33 ` William Kenworthy
2014-05-11 8:53 ` Mick
2014-05-11 10:43 ` William Kenworthy
2014-05-11 12:29 ` Peter Humphrey
2014-05-11 15:53 ` Alan McKinnon
2014-05-12 14:08 ` Marc Joliet
2014-05-12 14:39 ` Peter Humphrey
2014-05-12 15:04 ` Marc Joliet
2014-05-12 16:15 ` Dale
2014-05-12 19:12 ` Marc Joliet
2014-05-12 19:28 ` Daniel Frey
2014-05-07 2:33 ` [gentoo-user] " Jonathan Callen
2014-05-16 20:15 ` [gentoo-user] experience thus far (was: planned btrfs conversion: questions) Marc Joliet
2014-05-16 20:43 ` Marc Joliet
2014-05-17 0:08 ` William Kenworthy [this message]
2014-05-17 0:44 ` [gentoo-user] experience thus far Marc Joliet
2014-05-17 3:02 ` William Kenworthy
2014-05-17 7:53 ` Mick
2014-05-17 11:41 ` Rich Freeman
2014-05-17 10:07 ` Neil Bothwick
2014-05-17 12:35 ` William Kenworthy
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=5376A871.7010609@iinet.net.au \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.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