Part of script: ================ btrfs filesystem sync cp -pR --reflink btrfs filesystem sync ================ So if another copy or two of script is starting in the moment, then first snapshot is making - then we receive ENOSPC.
-----Original Message----- From: Austin S. Hemmelgarn [mailto:[email protected]] Sent: Thursday, November 03, 2016 6:07 PM To: Peter Becker; Дмитрий Нечаев; linux-btrfs Subject: Re: Problem with btrfs snapshots On 2016-11-03 10:21, Peter Becker wrote: > (copy for mainlinglist) > > 2016-11-03 15:16 GMT+01:00 Дмитрий Нечаев <[email protected]>: > Yes. We tried "sync" in our script but it doesn't help. It works only > then we make one snapshot at a time. Even if we use "sync" before and > after creating snapshot, it doesn't help. You might try 'btrfs filesystem sync' called on the filesystem the snapshots are being created on. This works differently from the sync() syscall used by regular 'sync', and as a result forces metadata out as well as regular data (and it's almost certainly a metadata issue you are seeing), and it won't have as much impact on the rest of the system. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
