Joseph L. Casale wrote:
Well, I was thinking about vm and such, assuming at some point there was an OS
reading the filesystem tht can run rsync. But I concede the point, it
definitely makes things tricky.
It does seem there is some talk about the functionality, I assume it will
happen so
>Well, I was thinking about vm and such, assuming at some point there was an OS
>reading the filesystem tht can run rsync. But I concede the point, it
>definitely makes things tricky.
It does seem there is some talk about the functionality, I assume it will
happen sooner or later...
jlc
On Sun, Apr 13, 2008 at 11:54:36PM -0700, John R Pierce alleged:
> Garrick Staples wrote:
> >On Sun, Apr 13, 2008 at 11:21:28PM -0600, Joseph L. Casale alleged:
> >
> >>>Use rsync to copy the changes to the lv?
> >>>
> >>That would be only be possible if the lv had an fs that rsync and the
Joseph L. Casale wrote:
You need to start by reading some of the docs on LVM2.
eg. nothing stops you from mounting a snapshot back onto the same
mountpoint you snaped from.
I understand that, but where I am unsure is how space in the vg relates to
this? Will this not require much additio
:23:21 2008
Subject: Re: [CentOS] merge an lvm snapshot back
On Sun, Apr 13, 2008 at 07:59:20PM -0600, Joseph L. Casale alleged:
> >He wants to restore the real LV to the state it was in at the time one of
> >the snapshots was taken.
>
> Nah :)
> I want to sanp a volume, mount th
>You need to start by reading some of the docs on LVM2.
>
>eg. nothing stops you from mounting a snapshot back onto the same
>mountpoint you snaped from.
I understand that, but where I am unsure is how space in the vg relates to
this? Will this not require much additional space, what if I need to
Joseph L. Casale wrote:
Nah :)
I want to sanp a volume, mount the snap, do my `stuff`, if I like it, I can
merge into the primary copy and continue or dump the snap and go back...
You need to start by reading some of the docs on LVM2.
eg. nothing stops you from mounting a snapshot back onto
Garrick Staples wrote:
On Sun, Apr 13, 2008 at 11:21:28PM -0600, Joseph L. Casale alleged:
Use rsync to copy the changes to the lv?
That would be only be possible if the lv had an fs that rsync and the os under
rsync understood:)
If these are exported as block devices into xen vm's o
On Sun, Apr 13, 2008 at 11:21:28PM -0600, Joseph L. Casale alleged:
> >Use rsync to copy the changes to the lv?
>
> That would be only be possible if the lv had an fs that rsync and the os
> under rsync understood:)
> If these are exported as block devices into xen vm's or as iscsi targets for
>
>Use rsync to copy the changes to the lv?
That would be only be possible if the lv had an fs that rsync and the os under
rsync understood:)
If these are exported as block devices into xen vm's or as iscsi targets for
example it gets trickier.
jlc
___
On Sun, Apr 13, 2008 at 07:59:20PM -0600, Joseph L. Casale alleged:
> >He wants to restore the real LV to the state it was in at the time one of
> >the snapshots was taken.
>
> Nah :)
> I want to sanp a volume, mount the snap, do my `stuff`, if I like it, I can
> merge into the primary copy and c
>He wants to restore the real LV to the state it was in at the time one of
>the snapshots was taken.
Nah :)
I want to sanp a volume, mount the snap, do my `stuff`, if I like it, I can
merge into the primary copy and continue or dump the snap and go back...
That would be so very usefull! I know I
On Sun, 2008-04-13 at 08:47 -0700, Bart Schaefer wrote:
> On Sat, Apr 12, 2008 at 5:59 PM, Karanbir Singh <[EMAIL PROTECTED]> wrote:
> > well, just use it.
>
> This implies that "snapshot" is a bit of a misnomer for what LVM
> creates, because you can modify both the "snapshot" and the "real
> ph
On Sun, 2008-04-13 at 15:04 +0100, Karanbir Singh wrote:
> William L. Maltby wrote:
> > IIRC, you don't have a real snapshot on the LV ATM. The snapshot LV only
> > contains files that were chang(ed/ing) while the snapshot volume was
> > "attached" during the backup.
>
> That does not mean you can
Bart Schaefer wrote:
Also, your work flow is broken if your historic snapshots are now
production while the real physical LV isnt.( imho )
Seems to me that's exactly the situation he's trying to avoid. He
wants to restore the real LV to the state it was in at the time one of
the snapshots was
On Sat, Apr 12, 2008 at 5:59 PM, Karanbir Singh <[EMAIL PROTECTED]> wrote:
> well, just use it.
This implies that "snapshot" is a bit of a misnomer for what LVM
creates, because you can modify both the "snapshot" and the "real
physical LV," but if you want to be able to revert easily, it's the
"r
William L. Maltby wrote:
IIRC, you don't have a real snapshot on the LV ATM. The snapshot LV only
contains files that were chang(ed/ing) while the snapshot volume was
"attached" during the backup.
That does not mean you cant use the snapshot, as long as you are ready
to live with the fallouts
On Sun, 2008-04-13 at 01:59 +0100, Karanbir Singh wrote:
> Joseph L. Casale wrote:
> > So how does one accomplish this if say the snap is now deemed the copy of
> > interest? I am hoping dd is not the only answer:)
> >
>
> well, just use it.
>
> Also, your work flow is broken if your historic s
Joseph L. Casale wrote:
So how does one accomplish this if say the snap is now deemed the copy of
interest? I am hoping dd is not the only answer:)
well, just use it.
Also, your work flow is broken if your historic snapshots are now
production while the real physical LV isnt.( imho )
--
So how does one accomplish this if say the snap is now deemed the copy of
interest? I am hoping dd is not the only answer:)
Thanks!
jlc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
20 matches
Mail list logo
