OpenSolaris

Printable Version Enter a New Search
Bug ID 6421210
Synopsis zfs rollback without unmounting
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:zfs
Keywords
Responsible Engineer Matthew Ahrens
Reported Against snv_01
Duplicate Of
Introduced In
Commit to Fix snv_78
Fixed In snv_78
Release Fixed solaris_nevada(snv_78) , solaris_10u6(s10u6_01) (Bug ID:2160858)
Related Bugs 6421209 , 6635790 , 6658067 , 6661137
Submit Date 3-May-2006
Last Update Date 2-January-2008
Description
This RFE requests the ability to rollback a ZFS filesystem without unmounting the current filesystem. Right now, we see:

# zfs rollback space/test@recent
cannot unmount '/space/test': Device busy

This functionality would be required if users were to have their home directories on ZFS. A user can't unmount their home directory, as their current session would hold it open.

If this suppport is unfeasible, it would be nice if we could determine which files are open on that filesystem and which applications have them open, so that we could print an error along the lines of:

# zfs rollback space/test@recent
cannot rollback as the following programs are using this filesystem:
Firefox (pid 12345)
Text Editor (pid 67890)
Please exit these programs, and try again.

The current workaround would be to only allow the user to rollback filesystems which they're not using - but they'd need to know to create sub-filesystems of their home dir, rather than just creating directories as they do now, eg. have 

/tank/export/home/timf
/tank/export/home/timf/Documents
/tank/export/home/timf/public_html
etc.
Work Around
N/A
Comments
N/A