From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem hang on kernel 4.2.0 with copy reflink
Date: Sat, 9 Jan 2016 09:28:39 +0000 (UTC) [thread overview]
Message-ID: <pan$dc476$cfd1d0c9$da3d1c34$2b85f935@cox.net> (raw)
In-Reply-To: 568A6154.1060101@markandruth.co.uk
Mark Zealey posted on Mon, 04 Jan 2016 14:11:00 +0200 as excerpted:
> Also I have quota tracking enabled on the btrfs volume if that makes any
> difference.
I'm not sure whether it makes a difference for this particular hang, but
I do know that btrfs quotas are simply not stable thru at least 4.3. I'm
not sure what 4.4 status is, but my general recommendation regarding
btrfs quotas is...
If you need quotas, use a more mature filesystem where they work
reliably, if you don't, then turn them off for now, and don't turn them
on again until at least two complete kernel cycles have passed without a
known quota bug or instability, which, if 4.4 is indeed known-bug-free
and it and 4.5 remain so thru 4.6, means that would be the earliest I
could recommend turning it on, and that's only if there's no known quota
bugs in 4.4 or 4.5 or 4.6 by the time of 4.6 release.
Unless of course you're deliberately and specifically testing btrfs
quotas and working with the devs on fixing quota specific issues, in
which case, thank you. =:^)
Meanwhile, the rather long history of problems with quotas on btrfs is
both the reason I'm suggesting two complete cycles without quota issues
before enabling them, and a good reason to be skeptical as to current
releases' quota code or the likelihood of that two-releases-quota-bug-
free happening any time soon. There's definitely a lot of work going
into the feature and there's gotta be a point where it actually works,
but they've rewritten the code three times and are still dealing with
bugs, and it has been in a "try back in a couple kernel cycles" state for
years, now, so... who knows? Kinda reminds me of how long the raid56
code took, only quota was being worked on before that, and is still being
worked on, so...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2016-01-09 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 8:35 Filesystem hang on kernel 4.2.0 with copy reflink Mark Zealey
2016-01-04 10:41 ` Jack Wang
2016-01-04 12:11 ` Mark Zealey
2016-01-09 9:28 ` Duncan [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='pan$dc476$cfd1d0c9$da3d1c34$2b85f935@cox.net' \
--to=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).