Hello people. Thank you for your detailed replies, esp Duncan. In essence, I plan on using BTRFS for my production data -- mainly programs/documents I write in connection with my academic research. I'm not a professional sysadmin and I'm not running a business server. I'm just managing my own data, and as I have mentioned, my chief reason for looking at BTRFS is the ease of snapshots and backups using send/receive. It is clear now that snapshots are by and large stable but send/receive is not. But, IIUC, even if send/receive fails I still have the older data which is not overwritten due to COW and atomic operations, and I can always retry send/receive again. Is this correct? If yes, then I guess I can take the plunge but ensure I have daily backups (which BTRFS itself should help me do easily). -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
