On 11/28/2015 01:19 AM, Christoph Anton Mitterer wrote:
On Fri, 2015-11-27 at 17:16 +0800, Anand Jain wrote:
I understand as a user, a full md/lvm set of features are important
to begin operations using btrfs and we don't have it yet. I have to
blame it on the priority list.
What's
On Fri, 2015-11-27 at 17:16 +0800, Anand Jain wrote:
> I understand as a user, a full md/lvm set of features are important
> to begin operations using btrfs and we don't have it yet. I have to
> blame it on the priority list.
What's would be especially nice from the admin side, would be
On 11/27/2015 01:30 PM, Duncan wrote:
Ian Kelling posted on Thu, 26 Nov 2015 21:14:57 -0800 as excerpted:
I'd like to run "mail" when a btrfs raid drive fails, but I don't know
how to detect that a drive has failed. It don't see it in any docs.
Otherwise I assume I would never know until
Ian Kelling posted on Thu, 26 Nov 2015 21:14:57 -0800 as excerpted:
> I'd like to run "mail" when a btrfs raid drive fails, but I don't know
> how to detect that a drive has failed. It don't see it in any docs.
> Otherwise I assume I would never know until enough drives fail that the
> filesystem
On Thu, Nov 26, 2015, at 09:30 PM, Duncan wrote:
> What generally happens now, however, is that the btrfs will note failures
> attempting to write the device and start queuing up writes. If the
> device reappears fast enough, btrfs will flush the queue and be back to
> normal. Otherwise, you
