.\" 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_ATTR_MAKE_NON_RESIDENT" "9" "09 October 2005" "" ""

.SH NAME
ntfs_attr_make_non_resident \- convert a resident to a non-resident attribute
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int ntfs_attr_make_non_resident  (ntfs_inode * \fIni\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIni\fB\fR
ntfs inode describing the attribute to convert
.SH "DESCRIPTION"
.PP
Convert the resident ntfs attribute described by the ntfs inode \fIni\fR to a
non-resident one.
.PP
Return 0 on success and -errno on error.  The following error return codes
.SH "ARE DEFINED"
.PP
-EPERM - The attribute is not allowed to be non-resident.
-ENOMEM - Not enough memory.
-ENOSPC - Not enough disk space.
-EINVAL - Attribute not defined on the volume.
-EIO - I/o error or other error.
Note that -ENOSPC is also returned in the case that there is not enough
space in the mft record to do the conversion.  This can happen when the mft
record is already very full.  The caller is responsible for trying to make
space in the mft record and trying again.  FIXME: Do we need a separate
error return code for this kind of -ENOSPC or is it always worth trying
again in case the attribute may then fit in a resident state so no need to
make it non-resident at all?  Ho-hum...  (AIA)
.SH "NOTE TO SELF"
.PP
No changes in the attribute list are required to move from
a resident to a non-resident attribute.
.SH "LOCKING"
.PP
- The caller must hold i_sem on the inode.