Hello folks, I have a question and a small problem... I did try to replicate my zfs with all the snaps, so I did run few commands: time zfs send mypool/d at 2006_month_10 | zfs receive mypool2/d at 2006_month_10 real 6h35m12.34s user 0m0.00s sys 29m32.28s zfs send -i mypool/d at 2006_month_10 mypool/d at 2006_month_12 | zfs receive mypool/d at 2006_month_12 real 4h49m27.54s user 0m0.00s sys 13m40.87s zfs send -i mypool/d at 2006_month_12 mypool/d at 2007_month_01 | zfs receive mypool2/d at 2007_month_01 real 3h6m45.62s user 0m0.00s sys 12m58.73s zfs send -i mypool/d at 2007_month_01 mypool/d at 2007_month_02 | zfs receive mypool2/d at 2007_month_02 real 4h0m42.40s user 0m0.00s sys 17m49.84s zfs send -i mypool/d at 2007_month_02 mypool/d at 2007_month_03 | zfs receive mypool2/d at 2007_month_03 real 2h17m21.76s user 0m0.00s sys 10m9.26s zfs send -i mypool/d at 2007_month_03 mypool/d at month_04 | zfs receive mypool2/d at 2007_month_04 real 2h40m14.03s user 0m0.00s sys 11m37.35s then I was doing: zfs send -i mypool/d at month_04 mypool/d at day_14 | zfs receive mypool2/d at day_14 and my system rebooted (I tont think its related to the zfs send/receive, anyway when system started I did see that this partition was mounted. and when I did try to run that last command I got the following error: [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 mypool/d at day_14 | zfs receive mypool2/d at day_14 cannot receive: destination has been modified since most recent snapshot is there any way to do such replication by zfs send/receive and avoind such error message? Is there any way to force file system not to be mounted? Is there any way to make it maybe read only parition and then when its needed maybe make it live or whaverer? what I dont understand is that I did try to remove old snaps and still was getting those errors... Any suggestions? or advice as how I should proceed with this? Chris
On 4/17/07, Krzys <krzys at perfekt.net> wrote:> > > and when I did try to run that last command I got the following error: > [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 > mypool/d at day_14 | > zfs receive mypool2/d at day_14 > cannot receive: destination has been modified since most recent snapshot > > is there any way to do such replication by zfs send/receive and avoind > such > error message? Is there any way to force file system not to be mounted? Is > there > any way to make it maybe read only parition and then when its needed maybe > make > it live or whaverer?Check the -F option to zfs receive. This automatically rolls back the target. Nicholas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070417/ad549bbc/attachment.html>
[18:19:00] root at chrysek: /root > zfs send -i mypool/d at month_04 mypool/d
at day_14 |
zfs receive -F mypool2/d at day_14
invalid option ''F''
usage:
receive [-vn] <filesystem|volume|snapshot>
receive [-vn] -d <filesystem>
For the property list, run: zfs set|get
It does not seem to work unless I am doing it incorectly.
Chris
On Tue, 17 Apr 2007, Nicholas Lee wrote:
> On 4/17/07, Krzys <krzys at perfekt.net> wrote:
>>
>>
>> and when I did try to run that last command I got the following error:
>> [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04
>> mypool/d at day_14 |
>> zfs receive mypool2/d at day_14
>> cannot receive: destination has been modified since most recent
snapshot
>>
>> is there any way to do such replication by zfs send/receive and avoind
>> such
>> error message? Is there any way to force file system not to be mounted?
Is
>> there
>> any way to make it maybe read only parition and then when its needed
maybe
>> make
>> it live or whaverer?
>
>
> Check the -F option to zfs receive. This automatically rolls back the
> target.
> Nicholas
>
Ah, ok, not a problem, do you know Cindy when next Solaris Update is going to be released by SUN? Yes, I am running U3 at this moment. Regards, Chris On Mon, 16 Apr 2007, Cindy.Swearingen at Sun.COM wrote:> Chris, > > Looks like you''re not running a Solaris release that contains > the zfs receive -F option. This option is in current Solaris community > release, build 48. > > http://docs.sun.com/app/docs/doc/817-2271/6mhupg6f1?a=view#gdsup > > Otherwise, you''ll have to wait until an upcoming Solaris 10 release. > > Cindy > > Krzys wrote: >> [18:19:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >> mypool/d at day_14 | zfs receive -F mypool2/d at day_14 >> invalid option ''F'' >> usage: >> receive [-vn] <filesystem|volume|snapshot> >> receive [-vn] -d <filesystem> >> >> For the property list, run: zfs set|get >> >> It does not seem to work unless I am doing it incorectly. >> >> Chris >> >> On Tue, 17 Apr 2007, Nicholas Lee wrote: >> >>> On 4/17/07, Krzys <krzys at perfekt.net> wrote: >>> >>>> >>>> >>>> and when I did try to run that last command I got the following error: >>>> [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >>>> mypool/d at day_14 | >>>> zfs receive mypool2/d at day_14 >>>> cannot receive: destination has been modified since most recent snapshot >>>> >>>> is there any way to do such replication by zfs send/receive and avoind >>>> such >>>> error message? Is there any way to force file system not to be mounted? >>>> Is >>>> there >>>> any way to make it maybe read only parition and then when its needed >>>> maybe >>>> make >>>> it live or whaverer? >>> >>> >>> >>> Check the -F option to zfs receive. This automatically rolls back the >>> target. >>> Nicholas >>> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > !DSPAM:122,4623fa8a1809423226276! >
Chris, Looks like you''re not running a Solaris release that contains the zfs receive -F option. This option is in current Solaris community release, build 48. http://docs.sun.com/app/docs/doc/817-2271/6mhupg6f1?a=view#gdsup Otherwise, you''ll have to wait until an upcoming Solaris 10 release. Cindy Krzys wrote:> [18:19:00] root at chrysek: /root > zfs send -i mypool/d at month_04 > mypool/d at day_14 | zfs receive -F mypool2/d at day_14 > invalid option ''F'' > usage: > receive [-vn] <filesystem|volume|snapshot> > receive [-vn] -d <filesystem> > > For the property list, run: zfs set|get > > It does not seem to work unless I am doing it incorectly. > > Chris > > On Tue, 17 Apr 2007, Nicholas Lee wrote: > >> On 4/17/07, Krzys <krzys at perfekt.net> wrote: >> >>> >>> >>> and when I did try to run that last command I got the following error: >>> [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >>> mypool/d at day_14 | >>> zfs receive mypool2/d at day_14 >>> cannot receive: destination has been modified since most recent snapshot >>> >>> is there any way to do such replication by zfs send/receive and avoind >>> such >>> error message? Is there any way to force file system not to be >>> mounted? Is >>> there >>> any way to make it maybe read only parition and then when its needed >>> maybe >>> make >>> it live or whaverer? >> >> >> >> Check the -F option to zfs receive. This automatically rolls back the >> target. >> Nicholas >> > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 16/04/07, Krzys <krzys at perfekt.net> wrote:> Ah, ok, not a problem, do you know Cindy when next Solaris Update is going to be > released by SUN? Yes, I am running U3 at this moment.Summer is what I last read (July?). -- "Less is only more where more is no good." --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/
Chris, This option will be available in the upcoming Solaris 10 release, a few months from now. We''ll send out a listing of the new ZFS features around that time. Cindy Krzys wrote:> Ah, ok, not a problem, do you know Cindy when next Solaris Update is > going to be released by SUN? Yes, I am running U3 at this moment. > > Regards, > > Chris > > On Mon, 16 Apr 2007, Cindy.Swearingen at Sun.COM wrote: > >> Chris, >> >> Looks like you''re not running a Solaris release that contains >> the zfs receive -F option. This option is in current Solaris community >> release, build 48. >> >> http://docs.sun.com/app/docs/doc/817-2271/6mhupg6f1?a=view#gdsup >> >> Otherwise, you''ll have to wait until an upcoming Solaris 10 release. >> >> Cindy >> >> Krzys wrote: >> >>> [18:19:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >>> mypool/d at day_14 | zfs receive -F mypool2/d at day_14 >>> invalid option ''F'' >>> usage: >>> receive [-vn] <filesystem|volume|snapshot> >>> receive [-vn] -d <filesystem> >>> >>> For the property list, run: zfs set|get >>> >>> It does not seem to work unless I am doing it incorectly. >>> >>> Chris >>> >>> On Tue, 17 Apr 2007, Nicholas Lee wrote: >>> >>>> On 4/17/07, Krzys <krzys at perfekt.net> wrote: >>>> >>>>> >>>>> >>>>> and when I did try to run that last command I got the following error: >>>>> [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >>>>> mypool/d at day_14 | >>>>> zfs receive mypool2/d at day_14 >>>>> cannot receive: destination has been modified since most recent >>>>> snapshot >>>>> >>>>> is there any way to do such replication by zfs send/receive and avoind >>>>> such >>>>> error message? Is there any way to force file system not to be >>>>> mounted? Is >>>>> there >>>>> any way to make it maybe read only parition and then when its >>>>> needed maybe >>>>> make >>>>> it live or whaverer? >>>> >>>> >>>> >>>> >>>> Check the -F option to zfs receive. This automatically rolls back the >>>> target. >>>> Nicholas >>>> >>> _______________________________________________ >>> zfs-discuss mailing list >>> zfs-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> >> >> !DSPAM:122,4623fa8a1809423226276! >> > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Ok, so -F option is not in U3, is there any way to replicate file system and not be able to mount it automatically? so when I do zfs send/receive it wont be mounted and changes would not be made so that further replications could be possible? What I did notice was that if I am doing zfs send/receive right one after another I am able to replicate all my snaps, but when I wait a day or even few hours I get notice that file system got changed, and that is because it was mounted and I guess because of that I am not able to perform any more snaps to be send... any idea what I could do meanwhile I am waiting for -F? Thank you. Chris On Tue, 17 Apr 2007, Nicholas Lee wrote:> On 4/17/07, Krzys <krzys at perfekt.net> wrote: >> >> >> and when I did try to run that last command I got the following error: >> [16:26:00] root at chrysek: /root > zfs send -i mypool/d at month_04 >> mypool/d at day_14 | >> zfs receive mypool2/d at day_14 >> cannot receive: destination has been modified since most recent snapshot >> >> is there any way to do such replication by zfs send/receive and avoind >> such >> error message? Is there any way to force file system not to be mounted? Is >> there >> any way to make it maybe read only parition and then when its needed maybe >> make >> it live or whaverer? > > > Check the -F option to zfs receive. This automatically rolls back the > target. > Nicholas > > > !DSPAM:122,4623f42c1444623226276! >
Hi, Krzys wrote:> Ok, so -F option is not in U3, is there any way to replicate file system > and not be able to mount it automatically? so when I do zfs send/receive > it wont be mounted and changes would not be made so that further > replications could be possible? What I did notice was that if I am doing > zfs send/receive right one after another I am able to replicate all my > snaps, but when I wait a day or even few hours I get notice that file > system got changed, and that is because it was mounted and I guess > because of that I am not able to perform any more snaps to be send... > any idea what I could do meanwhile I am waiting for -F?this should work: zfs unmount pool/filesystem zfs rollback (latest snapshot) zfs send ... | zfs receive zfs mount pool/filesystem Better yet: Assuming you don''t actually want to use the filesystem you replicate to, but just use it as a sink for backup purposes, you can mark it unmountable, then just send stuff to it. zfs set canmount=off pool/filesystem zfs rollback (latest snapshot, one last time) Then, whenever you want to access the receiving filesystem, clone it. Hope this helps, Constantin -- Constantin Gonzalez Sun Microsystems GmbH, Germany Platform Technology Group, Global Systems Engineering http://www.sun.de/ Tel.: +49 89/4 60 08-25 91 http://blogs.sun.com/constantin/ Sitz d. Ges.: Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Marcel Schneider, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering
It does not work, I did try to remove every snap and I ended destroying that pool all together and had to resend it all.. My goal is to use zfs send/receive for backup purposes to big storage system that I have, and keep snaps, I dont care if file system is mounted or not but I want to have ability every month to be able to send changes to it and update with current incremental snaps... but because of the main disk is beeing mounted, even that I dont go there it changes something on it like access times or something and that prevents me from sending incremental zfs snaps... :( So that -F option will work but its few months away from what I understand... and I would like to just do zfs send/receive now and keep updating it monthly or even daily. Regards, Chris On Fri, 20 Apr 2007, Constantin Gonzalez wrote:> Hi, > > Krzys wrote: >> Ok, so -F option is not in U3, is there any way to replicate file system >> and not be able to mount it automatically? so when I do zfs send/receive >> it wont be mounted and changes would not be made so that further >> replications could be possible? What I did notice was that if I am doing >> zfs send/receive right one after another I am able to replicate all my >> snaps, but when I wait a day or even few hours I get notice that file >> system got changed, and that is because it was mounted and I guess >> because of that I am not able to perform any more snaps to be send... >> any idea what I could do meanwhile I am waiting for -F? > > this should work: > > zfs unmount pool/filesystem > zfs rollback (latest snapshot) > zfs send ... | zfs receive > zfs mount pool/filesystem > > Better yet: Assuming you don''t actually want to use the filesystem you > replicate to, but just use it as a sink for backup purposes, you can mark > it unmountable, then just send stuff to it. > > zfs set canmount=off pool/filesystem > zfs rollback (latest snapshot, one last time) > > Then, whenever you want to access the receiving filesystem, clone it. > > Hope this helps, > Constantin > > -- > Constantin Gonzalez Sun Microsystems GmbH, Germany > Platform Technology Group, Global Systems Engineering http://www.sun.de/ > Tel.: +49 89/4 60 08-25 91 http://blogs.sun.com/constantin/ > > Sitz d. Ges.: Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten > Amtsgericht Muenchen: HRB 161028 > Geschaeftsfuehrer: Marcel Schneider, Wolfgang Engels, Dr. Roland Boemer > Vorsitzender des Aufsichtsrates: Martin Haering > > > !DSPAM:122,4628d32121915021468! >
Krzys wrote:> It does not work, I did try to remove every snap and I ended destroying > that pool all together and had to resend it all.. My goal is to use zfs > send/receive for backup purposes to big storage system that I have, and > keep snaps, I dont care if file system is mounted or not but I want to > have ability every month to be able to send changes to it and update > with current incremental snaps... but because of the main disk is beeing > mounted, even that I dont go there it changes something on it like > access times or something and that prevents me from sending incremental > zfs snaps... :( So that -F option will work but its few months away from > what I understand... and I would like to just do zfs send/receive now > and keep updating it monthly or even daily.If the filesystem you are doing the incremental ''zfs recv'' into is always unmounted, you should not see the "fs modified since last snapshot" error. Can you send the specific commands / output that you''re seeing? Is a crash / power loss involved? Also note, ''zfs set mountpoint=none'' is the preferred method to not mount a filesystem + its descendents. --matt