linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 40TB volume taking over 16 hours to mount, any ideas?
Date: Sat, 9 Aug 2014 23:57:19 -0500	[thread overview]
Message-ID: <CAKcLGm8u_oGqwnCNQsazhVcY2ZC2-kAzATbLA9k+_OUGDVYSHQ@mail.gmail.com> (raw)
In-Reply-To: <pan$b3507$daae2ab8$2945c916$3e96ccb9@cox.net>

On Sat, Aug 9, 2014 at 11:21 PM, Duncan <1i5t5.duncan@cox.net> wrote:

> ....  But from rc5 on thru rc7 or 8 and
> release, unless you're one of the ones still waiting on a bug found
> earlier to be fixed, it's generally quite stable and boring.
>
> So by the time of actual .0 release, it really is quite stable, and no
> longer development kernel.  Sure, Greg KH's stable series kernel releases
> stabilize it further, but that's exactly what they are, stable series,
> not development series, and there's really no development going into it
> generally from rc1 on, tho occasionally something that needs to come
> after everything else is slipped in in the first couple days after rc1,
> but still well before rc2, and the .0 release signifies the end of the
> post development stabilization period such that .0 really is no longer a
> development kernel at all, even if there are a few more weekly stable-
> series updates (about 10, 3.15.10 was announced to be the last one for
> 3.15, with the Friday-released 3.15.9) before support ceases if it's not
> a long-term-stable candidate.
>

I can't say I've observed that to be the case with Btrfs.  I know
there is a core group of developers working very hard on testing the
Btrfs updates in the _rc kernels, but once that .0 kernel hits the
streets, the extra exposure to all the various combinations of
hardware and options has been know to discover new issues.  I think
this is nearly unavoidable given the pace of Btrfs development.

  reply	other threads:[~2014-08-10  4:57 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
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 [this message]
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=CAKcLGm8u_oGqwnCNQsazhVcY2ZC2-kAzATbLA9k+_OUGDVYSHQ@mail.gmail.com \
    --to=mitch.harder@sabayonlinux.org \
    --cc=1i5t5.duncan@cox.net \
    --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).