From: Michael Russo <mike@papersolve.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Mon, 3 Mar 2014 19:24:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20140303T200845-874@post.gmane.org> (raw)
In-Reply-To: D35E6741-2350-4910-B785-5584F730EDA9@colorremedies.com
Chris Murphy <lists <at> colorremedies.com> writes:
> It might be worth adding enospc_debug as a mount option
These messages only appear when I mount with enospc_debug. I
included them as examples but I can post the full output later if
needed. As for whether btrfs-convert should be recommended, I
mean probably not, but when you've got a big media drive filled
with music, pictures, and movies, with no other place to store it,
and you've experienced corruption where 5% of your MP3 files
have 10 seconds of another MP3 stuck in the middle of them
somehow, and suddenly realize you NEED a checksumming
next-generation file system like btrfs, you're going to convert!
next prev parent reply other threads:[~2014-03-03 19:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:23 ENOSPC errors during raid1 rebalance Mike Russo
2014-03-03 18:16 ` Duncan
2014-03-03 18:24 ` Michael Russo
2014-03-03 18:48 ` Chris Murphy
2014-03-03 19:24 ` Michael Russo [this message]
2014-03-03 20:41 ` Chris Murphy
2014-03-03 20:50 ` Michael Russo
2014-03-03 21:02 ` Chris Murphy
2014-03-03 18:39 ` Hugo Mills
2014-03-04 15:55 ` Michael Russo
2014-03-04 17:29 ` Chris Murphy
2014-03-04 18:54 ` Michael Russo
2014-03-04 19:30 ` Chris Murphy
2014-03-05 0:27 ` Mike Russo
2014-03-05 3:32 ` Chris Murphy
2014-03-05 22:13 ` Michael Russo
2014-03-06 7:41 ` Duncan
2014-03-07 1:13 ` Michael Russo
2014-03-07 8:02 ` Hugo Mills
2014-03-07 10:18 ` Duncan
2014-03-07 14:17 ` Mike Russo
2014-03-08 1:46 ` Mike Russo
2014-03-05 4:08 ` Chris Murphy
2014-03-05 22:13 ` Michael Russo
2014-03-06 17:07 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2014-03-13 22:38 Eugene Crosser
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=loom.20140303T200845-874@post.gmane.org \
--to=mike@papersolve.com \
--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