On 05/07/2014 01:39 PM, Marc MERLIN wrote:
> On Wed, May 07, 2014 at 11:35:52AM +, Duncan wrote:
>> Marc MERLIN posted on Wed, 07 May 2014 01:56:12 -0700 as excerpted:
>>
>>> On Tue, May 06, 2014 at 04:26:48PM +, Duncan wrote:
Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as ex
On Wed, May 07, 2014 at 11:35:52AM +, Duncan wrote:
> Marc MERLIN posted on Wed, 07 May 2014 01:56:12 -0700 as excerpted:
>
> > On Tue, May 06, 2014 at 04:26:48PM +, Duncan wrote:
> >> Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as excerpted:
> >>
> >> >
> >> > Aaah, right, you
Marc MERLIN posted on Wed, 07 May 2014 01:56:12 -0700 as excerpted:
> On Tue, May 06, 2014 at 04:26:48PM +, Duncan wrote:
>> Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as excerpted:
>>
>> >
>> > Aaah, right, you can use a script to see the file differences between
>> > two snapsho
On Tue, May 06, 2014 at 04:26:48PM +, Duncan wrote:
> Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as excerpted:
>
> > On Mon, May 05, 2014 at 01:36:39AM +0100, Hugo Mills wrote:
> >>I'm guessing it involves reflink copies of files from the snapshot
> >> back to the "original", an
Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as excerpted:
> On Mon, May 05, 2014 at 01:36:39AM +0100, Hugo Mills wrote:
>>I'm guessing it involves reflink copies of files from the snapshot
>> back to the "original", and then restarting affected services. That's
>> about the only othe
Marc MERLIN posted on Sat, 03 May 2014 17:52:57 -0700 as excerpted:
> (more questions I'm asking myself while writing my talk slides)
>
> I know Suse uses btrfs to roll back filesystem changes.
>
> So I understand how you can take a snapshot before making a change, but
> not how you revert to th
On Sun, May 04, 2014 at 09:23:12PM -0600, Chris Murphy wrote:
>
> On May 4, 2014, at 5:26 PM, Marc MERLIN wrote:
>
> > Actually, never mind Suse, does someone know whether you can revert to
> > an older snapshot in place?
>
> They are using snapper. Updates are not atomic, that is they
> are ap
On Mon, May 05, 2014 at 01:36:39AM +0100, Hugo Mills wrote:
>I'm guessing it involves reflink copies of files from the snapshot
> back to the "original", and then restarting affected services. That's
> about the only other thing that I can think of, but it's got load of
> race conditions in it
On May 4, 2014, at 5:26 PM, Marc MERLIN wrote:
> Actually, never mind Suse, does someone know whether you can revert to
> an older snapshot in place?
They are using snapper. Updates are not atomic, that is they are applied to the
currently mounted fs, not the snapshot, and after update the sys
On Sun, May 04, 2014 at 04:26:45PM -0700, Marc MERLIN wrote:
> Actually, never mind Suse, does someone know whether you can revert to
> an older snapshot in place?
Not while the system's running useful services, no.
> The only way I can think of is to mount the snapshot on top of the other
> f
Actually, never mind Suse, does someone know whether you can revert to
an older snapshot in place?
The only way I can think of is to mount the snapshot on top of the other
filesystem. This gets around the umounting a filesystem with open
filehandles problem, but this also means that you have to kee
(more questions I'm asking myself while writing my talk slides)
I know Suse uses btrfs to roll back filesystem changes.
So I understand how you can take a snapshot before making a change, but
not how you revert to that snapshot without rebooting or using rsync,
How do you do a pivot-root like mo
12 matches
Mail list logo
