1994-05-26 06:35:07 +00:00
|
|
|
.\" Copyright (c) 1980, 1993
|
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
|
.\"
|
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
|
.\" are met:
|
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
2017-02-28 23:42:47 +00:00
|
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
1994-05-26 06:35:07 +00:00
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
|
.\"
|
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
|
.\"
|
|
|
|
|
.\" @(#)clri.8 8.2 (Berkeley) 4/19/94
|
1999-08-28 00:22:10 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-26 06:35:07 +00:00
|
|
|
.\"
|
2016-10-05 20:01:09 +00:00
|
|
|
.Dd October 5, 2016
|
1994-05-26 06:35:07 +00:00
|
|
|
.Dt CLRI 8
|
2001-07-10 11:04:34 +00:00
|
|
|
.Os
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh NAME
|
|
|
|
|
.Nm clri
|
|
|
|
|
.Nd clear an inode
|
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1994-05-26 06:35:07 +00:00
|
|
|
.Ar special_device inode_number ...
|
|
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
.Bf -symbolic
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
|
.Nm
|
2002-08-21 18:11:48 +00:00
|
|
|
utility is obsoleted for normal file system repair work by
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr fsck 8 .
|
|
|
|
|
.Ef
|
|
|
|
|
.Pp
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
|
.Nm
|
2002-10-18 01:05:46 +00:00
|
|
|
utility zeroes out the inodes with the specified inode number(s)
|
2002-08-21 18:11:48 +00:00
|
|
|
on the file system residing on the given
|
1994-05-26 06:35:07 +00:00
|
|
|
.Ar special_device .
|
|
|
|
|
The
|
|
|
|
|
.Xr fsck 8
|
|
|
|
|
utility is usually run after
|
1998-06-04 06:44:18 +00:00
|
|
|
.Nm
|
|
|
|
|
to reclaim the zeroed inode(s) and the
|
1994-05-26 06:35:07 +00:00
|
|
|
blocks previously claimed by those inode(s).
|
|
|
|
|
Both read and write permission are required on the specified
|
|
|
|
|
.Ar special_device .
|
|
|
|
|
.Pp
|
|
|
|
|
The primary purpose of this routine
|
|
|
|
|
is to remove a file which
|
|
|
|
|
for some reason is not being properly handled by
|
|
|
|
|
.Xr fsck 8 .
|
|
|
|
|
Once removed,
|
|
|
|
|
it is anticipated that
|
|
|
|
|
.Xr fsck 8
|
|
|
|
|
will be able to clean up the resulting mess.
|
1998-06-04 06:44:18 +00:00
|
|
|
.Sh SEE ALSO
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr fsck 8 ,
|
1997-01-13 00:25:51 +00:00
|
|
|
.Xr fsdb 8
|
2016-10-05 20:01:09 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
|
The
|
|
|
|
|
.Nm
|
|
|
|
|
utility first appeared in
|
|
|
|
|
.At v6 .
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh BUGS
|
|
|
|
|
If the file is open, the work of
|
1998-06-04 06:44:18 +00:00
|
|
|
.Nm
|
1994-05-26 06:35:07 +00:00
|
|
|
will be lost when the inode is written back to disk from the inode cache.
|
