Constantin Gonzalez
2007-Apr-12 09:30 UTC
[zfs-discuss] Who modified my ZFS receive destination?
Hi, I''m currently migrating a filesystem from one pool to the other through a series of zfs send/receive commands in order to preserve all snapshots. But at some point, zfs receive says "cannot receive: destination has been modified since most recent snapshot". I am pretty sure nobody changed anything at my destination filesystem and I also tried rolling back to an earlier snapshot on the destination filesystem to make it clean again. Here''s an excerpt of the snapshots on my source filesystem: # zfs list -rt snapshot pelotillehue/constant NAME USED AVAIL REFER MOUNTPOINT pelotillehue/constant at 200609172014 236K - 33.6G - pelotillehue/constant at 200610061100 747K - 46.0G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 3.07G - 116G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 18.9M - 115G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 10.9M - 115G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 606M - 105G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 167M - 105G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 5.31M - 105G - pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 1.90M - 105G - pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 1.26M - 105G - pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 15.2M - 109G - pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-15-00:00:00 17.5M - 109G - ... (further lines omitted) On the destination filesystem, snapshots have been replicated through zfs send/receive up to the 2007-01-01 snapshot, so I do the following: # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 | zfs receive santiago/home/constant This worked, but now, only seconds later: # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs receive santiago/home/constant cannot receive: destination has been modified since most recent snapshot Fails. So I try rolling back to the 2007-01-08 snapshot on the destination filesystem to be clean again, but: # zfs rollback santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs receive santiago/home/constant cannot receive: destination has been modified since most recent snapshot Hmm, why does ZFS think my destination has been modified, although I didn''t do anything? Another peculiar thing: zfs list on the destination snapshots says: # zfs list -rt snapshot santiago/home/constant NAME USED AVAIL REFER MOUNTPOINT santiago/home/constant at 200609172014 189K - 33.6G - santiago/home/constant at 200610061100 670K - 46.0G - santiago/home/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 3.07G - 116G - santiago/home/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 18.4M - 115G - santiago/home/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 10.5M - 115G - santiago/home/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 603M - 105G - santiago/home/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 163M - 105G - santiago/home/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 4.87M - 105G - santiago/home/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 1.79M - 106G - santiago/home/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 1.16M - 106G - santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 57K - 109G - Note that the Used column for the 2007-01-08 snapshot says 57K on the destination, but 15.2M on the source. Could it be that the reception of the 2007-01-08 failed and ZFS didn''t notice? I''ve tried this multiple times, including destroying snapshots and rolling back on the destination to the 2007-01-01 state, so what you see above is already a second try of the same. The other values vary too, but only slightly. Compression is turned on on both pools. The source pool has been scrubbed on Monday with no known data errors and the destination pool is brand new and I''m scrubbing it as we speak. Best regards, 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
Trevor Watson
2007-Apr-12 10:30 UTC
[zfs-discuss] Who modified my ZFS receive destination?
Hi Constantin, I had the same problem, and the solution was to make sure that the filesystem is not mounted on the destination system when you perform the zfs recv (zfs set mountpoint=none santiago/home). Trev Constantin Gonzalez wrote:> Hi, > > I''m currently migrating a filesystem from one pool to the other through > a series of zfs send/receive commands in order to preserve all snapshots. > > But at some point, zfs receive says "cannot receive: destination has been > modified since most recent snapshot". I am pretty sure nobody changed anything > at my destination filesystem and I also tried rolling back to an earlier > snapshot on the destination filesystem to make it clean again. > > Here''s an excerpt of the snapshots on my source filesystem: > > # zfs list -rt snapshot pelotillehue/constant > NAME USED AVAIL > REFER MOUNTPOINT > pelotillehue/constant at 200609172014 236K - > 33.6G - > pelotillehue/constant at 200610061100 747K - > 46.0G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 3.07G - > 116G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 18.9M - > 115G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 10.9M - > 115G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 606M - > 105G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 167M - > 105G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 5.31M - > 105G - > pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 1.90M - > 105G - > pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 1.26M - > 105G - > pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 15.2M - > 109G - > pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-15-00:00:00 17.5M - > 109G - > > ... (further lines omitted) > > > On the destination filesystem, snapshots have been replicated through > zfs send/receive up to the 2007-01-01 snapshot, so I do the following: > > # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 > pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 | zfs receive > santiago/home/constant > > This worked, but now, only seconds later: > > # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 > pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs receive > santiago/home/constant > cannot receive: destination has been modified since most recent snapshot > > Fails. So I try rolling back to the 2007-01-08 snapshot on the destination > filesystem to be clean again, but: > > # zfs rollback santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 > # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 > pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs receive > santiago/home/constant > cannot receive: destination has been modified since most recent snapshot > > Hmm, why does ZFS think my destination has been modified, although I didn''t > do anything? > > Another peculiar thing: zfs list on the destination snapshots says: > > # zfs list -rt snapshot santiago/home/constant > NAME USED AVAIL > REFER MOUNTPOINT > santiago/home/constant at 200609172014 189K - > 33.6G - > santiago/home/constant at 200610061100 670K - > 46.0G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 3.07G - > 116G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 18.4M - > 115G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 10.5M - > 115G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 603M - > 105G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 163M - > 105G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 4.87M - > 105G - > santiago/home/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 1.79M - > 106G - > santiago/home/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 1.16M - > 106G - > santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 57K - > 109G - > > Note that the Used column for the 2007-01-08 snapshot says 57K on the > destination, but 15.2M on the source. Could it be that the reception of > the 2007-01-08 failed and ZFS didn''t notice? > > I''ve tried this multiple times, including destroying snapshots and rolling > back on the destination to the 2007-01-01 state, so what you see above is > already a second try of the same. > > The other values vary too, but only slightly. Compression is turned on on > both pools. The source pool has been scrubbed on Monday with no known data > errors and the destination pool is brand new and I''m scrubbing it as we speak. > > Best regards, > Constantin >-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070412/45301ddc/attachment.bin>
Constantin Gonzalez
2007-Apr-12 11:51 UTC
[zfs-discuss] Who modified my ZFS receive destination?
Hi Trev, Trevor Watson wrote:> Hi Constantin, > > I had the same problem, and the solution was to make sure that the > filesystem is not mounted on the destination system when you perform the > zfs recv (zfs set mountpoint=none santiago/home).thanks! This time it worked: # zfs unmount santiago/home/constant # zfs rollback santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 # zfs send -i pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs receive santiago/home/constant # Still, this is kinda strange. This means, that we''ll need to zfs unmount, then zfs rollback <last snapshot> a lot when doing send/receive on a regular basis (as in weekly, daily, hourly, minutely cron-jobs) to be sure. Or keep any replicated filesystems unmounted _all_ the time. Best regards, Constantin> > Trev > > Constantin Gonzalez wrote: >> Hi, >> >> I''m currently migrating a filesystem from one pool to the other through >> a series of zfs send/receive commands in order to preserve all snapshots. >> >> But at some point, zfs receive says "cannot receive: destination has been >> modified since most recent snapshot". I am pretty sure nobody changed >> anything >> at my destination filesystem and I also tried rolling back to an earlier >> snapshot on the destination filesystem to make it clean again. >> >> Here''s an excerpt of the snapshots on my source filesystem: >> >> # zfs list -rt snapshot pelotillehue/constant >> NAME >> USED AVAIL >> REFER MOUNTPOINT >> pelotillehue/constant at 200609172014 >> 236K - >> 33.6G - >> pelotillehue/constant at 200610061100 >> 747K - >> 46.0G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 >> 3.07G - >> 116G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 >> 18.9M - >> 115G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 >> 10.9M - >> 115G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 >> 606M - >> 105G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 >> 167M - >> 105G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 >> 5.31M - >> 105G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 >> 1.90M - >> 105G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 >> 1.26M - >> 105G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 >> 15.2M - >> 109G - >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-15-00:00:00 >> 17.5M - >> 109G - >> >> ... (further lines omitted) >> >> >> On the destination filesystem, snapshots have been replicated through >> zfs send/receive up to the 2007-01-01 snapshot, so I do the following: >> >> # zfs send -i >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 | zfs >> receive >> santiago/home/constant >> >> This worked, but now, only seconds later: >> >> # zfs send -i >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs >> receive >> santiago/home/constant >> cannot receive: destination has been modified since most recent snapshot >> >> Fails. So I try rolling back to the 2007-01-08 snapshot on the >> destination >> filesystem to be clean again, but: >> >> # zfs rollback >> santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 >> # zfs send -i >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 >> pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 | zfs >> receive >> santiago/home/constant >> cannot receive: destination has been modified since most recent snapshot >> >> Hmm, why does ZFS think my destination has been modified, although I >> didn''t >> do anything? >> >> Another peculiar thing: zfs list on the destination snapshots says: >> >> # zfs list -rt snapshot santiago/home/constant >> NAME >> USED AVAIL >> REFER MOUNTPOINT >> santiago/home/constant at 200609172014 >> 189K - >> 33.6G - >> santiago/home/constant at 200610061100 >> 670K - >> 46.0G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06 >> 3.07G - >> 116G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00 >> 18.4M - >> 115G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03 >> 10.5M - >> 115G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00 >> 603M - >> 105G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01 >> 163M - >> 105G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00 >> 4.87M - >> 105G - >> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01 >> 1.79M - >> 106G - >> santiago/home/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01 >> 1.16M - >> 106G - >> santiago/home/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 >> 57K - >> 109G - >> >> Note that the Used column for the 2007-01-08 snapshot says 57K on the >> destination, but 15.2M on the source. Could it be that the reception of >> the 2007-01-08 failed and ZFS didn''t notice? >> >> I''ve tried this multiple times, including destroying snapshots and >> rolling >> back on the destination to the 2007-01-01 state, so what you see above is >> already a second try of the same. >> >> The other values vary too, but only slightly. Compression is turned on on >> both pools. The source pool has been scrubbed on Monday with no known >> data >> errors and the destination pool is brand new and I''m scrubbing it as >> we speak. >> >> Best regards, >> 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
Deron Hull
2007-Apr-12 14:20 UTC
[zfs-discuss] Re: Who modified my ZFS receive destination?
I noticed the same thing. You can not be sitting in the zfs directory on the remote system. Even if you have set it as readonly. I''m running a rolling snapshot+remote sync script and keep the pool unmounted on the remote system. This message posted from opensolaris.org
I can''t find the bugid on this one but it exists. You can use the
''-
F'' flag to ''zfs recv'' in the interim:
"
-F Force a rollback of the filesystem to the most
recent snapshot before performing the receive
operation.
"
eric
On Apr 12, 2007, at 2:30 AM, Constantin Gonzalez wrote:
> Hi,
>
> I''m currently migrating a filesystem from one pool to the other
> through
> a series of zfs send/receive commands in order to preserve all
> snapshots.
>
> But at some point, zfs receive says "cannot receive: destination
> has been
> modified since most recent snapshot". I am pretty sure nobody
> changed anything
> at my destination filesystem and I also tried rolling back to an
> earlier
> snapshot on the destination filesystem to make it clean again.
>
> Here''s an excerpt of the snapshots on my source filesystem:
>
> # zfs list -rt snapshot pelotillehue/constant
> NAME
> USED AVAIL
> REFER MOUNTPOINT
> pelotillehue/constant at 200609172014
> 236K -
> 33.6G -
> pelotillehue/constant at 200610061100
> 747K -
> 46.0G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06
> 3.07G -
> 116G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00
> 18.9M -
> 115G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03
> 10.9M -
> 115G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00
> 606M -
> 105G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01
> 167M -
> 105G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00
> 5.31M -
> 105G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01
> 1.90M -
> 105G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01
> 1.26M -
> 105G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00
> 15.2M -
> 109G -
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-15-00:00:00
> 17.5M -
> 109G -
>
> ... (further lines omitted)
>
>
> On the destination filesystem, snapshots have been replicated through
> zfs send/receive up to the 2007-01-01 snapshot, so I do the following:
>
> # zfs send -i pelotillehue/constant at zfs-auto-
> snap:nobackup-2007-01-01-00:00:01
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-01-08-00:00:00 |
> zfs receive
> santiago/home/constant
>
> This worked, but now, only seconds later:
>
> # zfs send -i pelotillehue/constant at zfs-auto-
> snap:nobackup-2007-01-08-00:00:00
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 |
> zfs receive
> santiago/home/constant
> cannot receive: destination has been modified since most recent
> snapshot
>
> Fails. So I try rolling back to the 2007-01-08 snapshot on the
> destination
> filesystem to be clean again, but:
>
> # zfs rollback santiago/home/constant at zfs-auto-
> snap:nobackup-2007-01-08-00:00:00
> # zfs send -i pelotillehue/constant at zfs-auto-
> snap:nobackup-2007-01-08-00:00:00
> pelotillehue/constant at zfs-auto-snap:nobackup-2007-02-15-00:00:01 |
> zfs receive
> santiago/home/constant
> cannot receive: destination has been modified since most recent
> snapshot
>
> Hmm, why does ZFS think my destination has been modified, although
> I didn''t
> do anything?
>
> Another peculiar thing: zfs list on the destination snapshots says:
>
> # zfs list -rt snapshot santiago/home/constant
> NAME
> USED AVAIL
> REFER MOUNTPOINT
> santiago/home/constant at 200609172014
> 189K -
> 33.6G -
> santiago/home/constant at 200610061100
> 670K -
> 46.0G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-11-22-00:00:06
> 3.07G -
> 116G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-11-29-00:00:00
> 18.4M -
> 115G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-01-00:00:03
> 10.5M -
> 115G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-08-00:00:00
> 603M -
> 105G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-15-00:00:01
> 163M -
> 105G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-22-00:00:00
> 4.87M -
> 105G -
> santiago/home/constant at zfs-auto-snap:nobackup-2006-12-29-00:00:01
> 1.79M -
> 106G -
> santiago/home/constant at zfs-auto-snap:nobackup-2007-01-01-00:00:01
> 1.16M -
> 106G -
> santiago/home/constant at zfs-auto-
> snap:nobackup-2007-01-08-00:00:00 57K -
> 109G -
>
> Note that the Used column for the 2007-01-08 snapshot says 57K on the
> destination, but 15.2M on the source. Could it be that the
> reception of
> the 2007-01-08 failed and ZFS didn''t notice?
>
> I''ve tried this multiple times, including destroying snapshots and
> rolling
> back on the destination to the 2007-01-01 state, so what you see
> above is
> already a second try of the same.
>
> The other values vary too, but only slightly. Compression is turned
> on on
> both pools. The source pool has been scrubbed on Monday with no
> known data
> errors and the destination pool is brand new and I''m scrubbing it
> as we speak.
>
> Best regards,
> 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
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Matthew Ahrens
2007-May-06 22:26 UTC
[zfs-discuss] Who modified my ZFS receive destination?
Constantin Gonzalez wrote:> But at some point, zfs receive says "cannot receive: destination has been > modified since most recent snapshot". I am pretty sure nobody changed anything > at my destination filesystem and I also tried rolling back to an earlier > snapshot on the destination filesystem to make it clean again.As Eric noted, you should use ''zfs recv -F'' to do a rollback if necessary. Also, you could use dtrace to figure out when the modification occurred, and by whom. We are also working on ''zfs diffs'' (RFE filed but id not handy), which would be able to tell you what was modified. --matt