<br><br>
<div class="gmail_quote">On Thu, Feb 17, 2011 at 1:55 AM, Alasdair G Kergon <span dir="ltr"><<a href="mailto:agk@redhat.com">agk@redhat.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">> > Is it possible to add timestamp and comment for each snapshots ?<br><br></div>Good idea - as a userspace lvm2 feature, yes.<br><br>We currently store creation details for each VG.<br>I agree we should also store such details for each LV.<br>
This should be optional, but default to enabled.<br>(People short of space can perhaps turn it off, discarding any existing<br>details.)<br><br>Storing a comment is perhaps an extension to tag support that's been discussed,<br>
to allow longer tags with a wider character set.<br></blockquote>
<div>U mean saving the snapshots timestamp infomation in VGDA?</div>
<div>It's not good i think. hundreds of snaps may be tagged but not attached using dmsetup create command.</div>
<div>saving attached snaps infomation in VGDA is more reasonable</div>
<div> </div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">> It should be noted that the above shared snapshot work is unlikely to<br>> make it upstream (portions of it likely will, for instance the lvm2<br>
> userspace changes). A new shared snapshot implementation is in<br>> development.<br><br>Different snapshot implementations are optimised for different types of usage.<br>Each one involves choosing between different trade-offs. We're unlikely ever<br>
to have one solution that is optimal for everyone.<br><br>In that spirit, I hope to be submitting more than one shared snapshot<br>implementation upstream, including *both* of the ones referred to in this<br>message. But I want the interfaces used by these implementations to be<br>
basically compatible so that the same userspace tools can make use of them.<br><font color="#888888"><br>Alasdair<br><br></font></blockquote></div><br>