On Thu, Oct 15, 2015 at 07:39:20AM +0200, audio muze wrote: > Thanks Chris > > I should've browsed recent threads, my apologies. Terribly > frustrating though that the issues you refer to aren't documented in > the btrfs wiki. Reading the wiki one is lead to believe that the only > real issue is the write hole that can occur as a result of a power > loss. There I was thinking I've a UPS attached, no problem. > Notification and handling of device failures is fundamental to any > raid system, so it seems it's nowhere near ready. >
Remember UPS does NOT protect against PSU failure, or a kernel crash.. -- Pasi > On Thu, Oct 15, 2015 at 7:06 AM, Chris Murphy <li...@colorremedies.com> wrote: > > See the other recent thread on the list "RAID6 stable enough for > > production?" > > > > A lot of your questions have already been answered in recent previous > > threads. > > > > While there are advantages to Btrfs raid56, there are some missing > > parts that make it incomplete and possibly unworkable for certain use > > cases. For example there's no notification of device failures like md > > and LVM raid. If there's a device failure, and then also any other > > problem crops up, the whole file system can become unusable. So > > whatever your backup strategy is going to be, it needs to be even more > > bulletproof if you're going to depend on Btrfs for production. > > > > > > -- > > Chris Murphy > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
