.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NTFS_EXTENT_MFT_RECORD_FREE" "9" "09 October 2005" "" ""

.SH NAME
ntfs_extent_mft_record_free \- free an extent mft record on an ntfs volume
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int ntfs_extent_mft_record_free  (ntfs_inode * \fIni\fB, MFT_RECORD * \fIm\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIni\fB\fR
ntfs inode of the mapped extent mft record to free
.TP
\fB\fIm\fB\fR
mapped extent mft record of the ntfs inode \fIni\fR
.SH "DESCRIPTION"
.PP
Free the mapped extent mft record \fIm\fR of the extent ntfs inode \fIni\fR\&.
.PP
Note that this function unmaps the mft record and closes and destroys \fIni\fR
internally and hence you cannot use either \fIni\fR nor \fIm\fR any more after this
function returns success.
.PP
On success return 0 and on error return -errno.  \fIni\fR and \fIm\fR are still valid
in this case and have not been freed.
.PP
For some errors an error message is displayed and the success code 0 is
returned and the volume is then left dirty on umount.  This makes sense in
case we could not rollback the changes that were already done since the
caller no longer wants to reference this mft record so it does not matter to
the caller if something is wrong with it as long as it is properly detached
from the base inode.