[zfs-discuss] zfs rollback without unmounting a file system

[Robert Milkowski]

Hello zfs-discuss,

  http://bugs.opensolaris.org/view_bug.do?bug_id=6421210

1. App opens and creates an empty file /pool/fs1/file1
2. zfs snapshot pool/[EMAIL PROTECTED]
3. App writes something to file and still keeps it open
4. zfs rollback pool/[EMAIL PROTECTED]

Now what happens to fd App is using? What is a file contents from App
point of view as long as it's still open?
New opens of that file will oen empy file I guess.


  

-- 
Best regards,
 Robert Milkowski  mailto:[EMAIL PROTECTED]
 http://milek.blogspot.com

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] zfs rollback without unmounting a file system

[can you guess?]

Allowing a filesystem to be rolled back without unmounting it sounds unwise, 
given the potentially confusing effect on any application with a file currently 
open there.

And if a user can't roll back their home directory filesystem, is that so bad?  
Presumably they can still access snapshot versions of individual files or even 
entire directory sub-trees and copy them to their current state if they want to 
- or whistle up someone else to perform a rollback of their home directory if 
they really need to.

I'm not normally one to advocate protecting users from themselves, but I do 
think that applications have some rights to believe that there are some 
guarantees about stability as long as they have a file accessed (and that the 
system should terminate that access if it can't sustain those guarantees).

- bill
 
 
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss