If this isn't possible, is there a way to check a given path/filename on a btrfs filesystem, to show all the other reflinked path/filenames to the same file?
On Thu, Aug 27, 2015 at 3:31 AM, james harvey <jamespharve...@gmail.com> wrote: > I'm using btrfs and snapper. So, I have many periodic btrfs > snapshots, which are marked read-only (can of course be changed by > btrfs to r/w and changed back.) > > Let's say during my initial install I set a vimrc. And, let's say now > I want to change the vimrc, so that if I go back to any of the > snapshots my vimrc is the new one. Yeah, this totally re-writes > history, and goes against the idea of having historical backups. But > let's say that I change active snapshots often for testing and don't > want to keep having to re-change certain configuration files like > this. And I'm OK with blowing away my backups of the file. > > Right now, there should be only one copy of the vimrc file contents > that are being used/pointed to, since it's never been modified since > the very first snapshot. > > Is there a way I can modify the vimrc file, so that "all of them" are updated? > > Can I bypass copy on write during the edit, doing so just for the one > file, so any system files in he background still use COW? I see I > can't use chattr's NOCOW because the file isn't new or empty. Is > there another way? > > Or, do I have to edit the live file, turn all the snapshots to r/w, > perform a cp -ax --reflink=always to all the snapshot files, and turn > all the snapshots to r/o? There's a lot of snapshots to do this to. > (Granted a script would make this less painful.) -- 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
