From: Jose Ildefonso Camargo Tolosa <ildefonso.camargo@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 40TB volume taking over 16 hours to mount, any ideas?
Date: Mon, 11 Aug 2014 16:33:36 -0500 [thread overview]
Message-ID: <CAETJ_S_YDnJsf9Fc6+ynpBVK7MXv3RGuhhJrSVV2Tizf1J+kdA@mail.gmail.com> (raw)
In-Reply-To: <A7CFCD27-F663-425A-A695-3E7842777348@colorremedies.com>
As I hate when a thread is left "hanging", you deserve to know what
happened in the end, you likely already guessed, but anyway: I nuked
the filesystem, and started over.
After some internal discussion in the company, we decided to move to
ZFS for now. However, we will keep an eye on btrfs, and will likely
deploy it to some smaller system for further testing.
Thanks you all for your help!
Sincerely,
Ildefonso
next prev parent reply other threads:[~2014-08-11 21:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 21:35 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 3:38 ` Russell Coker
2014-08-09 14:32 ` Andy Smith
2014-08-09 14:58 ` Jose Ildefonso Camargo Tolosa
2014-08-09 16:06 ` Jose Ildefonso Camargo Tolosa
2014-08-09 17:01 ` Duncan
2014-08-09 18:21 ` Marc MERLIN
2014-08-10 4:03 ` Duncan
2014-08-10 12:43 ` Holger Hoffstätte
2014-08-10 14:39 ` Fixing the btrfs deadlocks Marc MERLIN
2014-08-10 15:42 ` Holger Hoffstätte
2014-08-10 16:36 ` Marc MERLIN
2014-08-09 18:38 ` 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 21:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 3:58 ` Jose Ildefonso Camargo Tolosa
2014-08-10 8:24 ` Duncan
2014-08-10 8:50 ` Timofey Titovets
2014-08-10 10:16 ` Duncan
2014-08-10 16:25 ` Chris Murphy
2014-08-11 21:33 ` Jose Ildefonso Camargo Tolosa [this message]
2014-08-12 4:15 ` Duncan
2014-08-12 14:24 ` Marc MERLIN
2014-08-13 2:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 4:21 ` Duncan
2014-08-10 4:57 ` Mitch Harder
2014-08-10 7:21 ` Duncan
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=CAETJ_S_YDnJsf9Fc6+ynpBVK7MXv3RGuhhJrSVV2Tizf1J+kdA@mail.gmail.com \
--to=ildefonso.camargo@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).