on 13/01/2014 18:50 Matthew Ahrens said the following: > Mounting the fs read-only, or using recv -F, seem like straightforward ways of > expressing the admin's intent. There are lots of other ways to > "inadvertently" > cause modifications to a filesystem (e.g. atime). Maybe we can make it easier > to do the right thing (e.g. flag to zfs recv that sets the readonly property?)
Good suggestion. I will think about this. > I could see making the delete queue transparent to the user by basically > delaying processing it until some other modification happens on the fs. That > way the filesystem doesn't diverge solely as a result of the delete queue. Another, crazier idea that I had was to virtually drain the delete queue while creating a send stream. That is, set size of the delete queue object to zero and include free object records for all IDs in the delete queue. -- Andriy Gapon _______________________________________________ developer mailing list developer@open-zfs.org http://lists.open-zfs.org/mailman/listinfo/developer
