188 
 189 
 190 
 191        /etc/vfstab
 192            list of default parameters for each file system
 193 
 194 
 195 ATTRIBUTES
 196        See attributes(5) for descriptions of the following attributes:
 197 
 198 
 199 
 200 
 201        +--------------------+-----------------+
 202        |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
 203        +--------------------+-----------------+
 204        |Interface Stability | Committed       |
 205        +--------------------+-----------------+
 206 
 207 SEE ALSO
 208        clri(1M), fsck_cachefs(1M), fsck_ufs(1M), fsdb_ufs(1M), fsirand(1M),
 209        fstyp(1M), mkfs(1M), mkfs_ufs(1M), mountall(1M), newfs(1M), reboot(
 210        1M), vfstab(4), attributes(5), largefile(5), ufs(7FS)
 211 
 212 WARNINGS
 213        The operating system buffers file system data. Running fsck on a
 214        mounted file system can cause the operating system's buffers to become
 215        out of date with respect to the disk. For this reason, the file system
 216        should be unmounted when fsck is used. If this is not possible, care
 217        should be taken that the system is quiescent and that it is rebooted
 218        immediately after fsck is run. Quite often, however, this will not be
 219        sufficient. A panic will probably occur if running fsck on a file
 220        system modifies the file system.
 221 
 222 NOTES
 223        This command may not be supported for all FSTypes.
 224 
 225 
 226        Starting with Solaris 9, fsck manages extended attribute data on the
 227        disk. (See fsattr(5) for a description of extended file attributes.) A
 228        file system with extended attributes can be mounted on versions of
 229        Solaris that are not attribute-aware (versions prior to Solaris 9), but
 230        the attributes will not be accessible and fsck will strip them from the
 231        files and place them in lost+found. Once the attributes have been
 232        stripped, the file system is completely stable on versions of Solaris
 233        that are not attribute-aware, but would be considered corrupted on
 234        attribute-aware versions. In the latter circumstance, run the attribute-
 235        aware fsck to stabilize the file system before using it in an
 236        attribute-aware environment.
 237 
 238 
 239 
 240                                   May 7, 2008                         FSCK(1M)

 188 
 189 
 190 
 191        /etc/vfstab
 192            list of default parameters for each file system
 193 
 194 
 195 ATTRIBUTES
 196        See attributes(5) for descriptions of the following attributes:
 197 
 198 
 199 
 200 
 201        +--------------------+-----------------+
 202        |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
 203        +--------------------+-----------------+
 204        |Interface Stability | Committed       |
 205        +--------------------+-----------------+
 206 
 207 SEE ALSO
 208        clri(1M), fsck_ufs(1M), fsdb_ufs(1M), fsirand(1M), fstyp(1M), mkfs(1M),
 209        mkfs_ufs(1M), mountall(1M), newfs(1M), reboot( 1M), vfstab(4),
 210        attributes(5), largefile(5), ufs(7FS)
 211 
 212 WARNINGS
 213        The operating system buffers file system data. Running fsck on a
 214        mounted file system can cause the operating system's buffers to become
 215        out of date with respect to the disk. For this reason, the file system
 216        should be unmounted when fsck is used. If this is not possible, care
 217        should be taken that the system is quiescent and that it is rebooted
 218        immediately after fsck is run. Quite often, however, this will not be
 219        sufficient. A panic will probably occur if running fsck on a file
 220        system modifies the file system.
 221 
 222 NOTES
 223        This command may not be supported for all FSTypes.
 224 
 225 
 226        Starting with Solaris 9, fsck manages extended attribute data on the
 227        disk. (See fsattr(5) for a description of extended file attributes.) A
 228        file system with extended attributes can be mounted on versions of
 229        Solaris that are not attribute-aware (versions prior to Solaris 9), but
 230        the attributes will not be accessible and fsck will strip them from the
 231        files and place them in lost+found. Once the attributes have been
 232        stripped, the file system is completely stable on versions of Solaris
 233        that are not attribute-aware, but would be considered corrupted on
 234        attribute-aware versions. In the latter circumstance, run the attribute-
 235        aware fsck to stabilize the file system before using it in an
 236        attribute-aware environment.
 237 
 238 
 239 
 240                                September 8, 2015                      FSCK(1M)