From: Peter Chant <pete@petezilla.co.uk>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Hardware failure or btrfs issue?
Date: Tue, 02 Jul 2013 22:37:07 +0100 [thread overview]
Message-ID: <51D34803.2010004@petezilla.co.uk> (raw)
In-Reply-To: <20130702174759.GB804@carfax.org.uk>
On 07/02/2013 06:48 PM, Hugo Mills wrote:
> So the damage probably happened then, if that stick is bad.
> Filesystems have this irritating habit of remembering things done to
> them across reboots. :) Hugo.
The previous action to the defrag was to delete 48 hours worth of
hourly snapshots. I was wondering if the numerous snapshots were what
was making defrag so painfully slow. Not that I know anything about
btrfs internals, but I suspect that is major enough action to catch out
any random corruption if there was any. I think I'll restrict snapshots
to once or twice a day at most unless that really should cause no issue.
Pete
prev parent reply other threads:[~2013-07-02 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:56 Hardware failure or btrfs issue? Peter Chant
2013-07-02 7:29 ` Hugo Mills
2013-07-02 17:36 ` Peter Chant
2013-07-02 17:48 ` Hugo Mills
2013-07-02 21:37 ` Peter Chant [this message]
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=51D34803.2010004@petezilla.co.uk \
--to=pete@petezilla.co.uk \
--cc=hugo@carfax.org.uk \
--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 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).