16.11.2017 19:13, Kai Krakow пишет: ... > > BTW: From user API perspective, btrfs snapshots do not guarantee > perfect granular consistent backups. Is it documented somewhere? I was relying on crash-consistent write-order-preserving snapshots in NetApp for as long as I remember. And I was sure btrfs offers is as it is something obvious for redirect-on-write idea. > A user-level file transaction may > still end up only partially in the snapshot. If you are running > transaction sensitive applications, those usually do provide some means > of preparing a freeze and a thaw of transactions. > Is snapshot creation synchronous to know when thaw? > I think the user transactions API which could've been used for this > will even be removed during the next kernel cycles. I remember > reiserfs4 tried to deploy something similar. But there's no consistent > layer in the VFS for subscribing applications to filesystem snapshots > so they could prepare and notify the kernel when they are ready. > I do not see what VFS has to do with it. NetApp works by simply preserving previous consistency point instead of throwing it away. I.e. snapshot is always last committed image on stable storage. Would something like this be possible on btrfs level by duplicating current on-disk root (sorry if I use wrong term)? ... -- 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
