Sorry to say, but this is the first point in the TODO List: Checkpoint rollback See http://www.nilfs.org/en/current_status.html However, I wonder if this has been worked on being the first point, I guess it should not be hard to do, isn't that what NILFS does on boot after an unclean shutdown? On Thu, May 20, 2010 at 5:17 PM, Rich Pixley <rich.pixley@xxxxxxxx> wrote: > > Can nilfs "roll back" to a previous state of the file system? > > For example, at some time = T(N), I have a file system in a known good state. So I check point it before taking a risky action. Then I take a risky action which leads me to the file system state at T(N+1). > > Sometimes, my risky action will be fine and I'll want to continue on. Other times, my risky action will result in a polluted, useless collection of data which I would like to discard. > > I understand that at time T(N+1) nilfs will allow me to create a checkpoint of T(N) which can be mounted read-only. What I'm asking is if nilfs can discard the state at T(N+1) and "roll back" to the state at T(N) as though T(N+1) had never happened. > > Can nilfs do this kind of "roll back"? > > --rich > -- > To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
