Skip to content
This repository
Fetching contributors…

Cannot retrieve contributors at this time

file 48 lines (44 sloc) 1.913 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
.TH FSSTAT 1
.SH NAME
fsstat \- Display general details of a file system
.SH SYNOPSIS
.B fsstat [-f
.I fstype
.B ] [-i imgtype] [-o imgoffset] [-b dev_sector_size] [-tvV]
.I image [images]
.SH DESCRIPTION
.B fsstat
displays the details associated with a file system. The output of this
command is file system specific. At a minimum, the range of meta-data
values (inode numbers) and content units (blocks or clusters) are given.
Also given are details from the Super Block, such as mount times and
and features. For file systems that use groups (FFS and EXT2FS), the
layout of each group is listed.

For a FAT file system, the FAT table is displayed in a condensed format.
Note that the data is in sectors and not in clusters.

.SH ARGUMENTS
.IP "-t type"
Print the file system type only.
.IP "-f fstype"
Specify the file system type.
Use '\-f list' to list the supported file system types.
If not given, autodetection methods are used.
.IP "-i imgtype"
Identify the type of image file, such as raw.
Use '\-i list' to list the supported types.
If not given, autodetection methods are used.
.IP "-o imgoffset"
The sector offset where the file system starts in the image.
.IP "-b dev_sector_size"
The size, in bytes, of the underlying device sectors. If not given, the value in the image format is used (if it exists) or 512-bytes is assumed.
.IP -v
Verbose output of debugging statements to stderr
.IP -V
Display version
.IP "image [images]"
The disk or partition image to read, whose format is given with '\-i'.
Multiple image file names can be given if the image is split into multiple segments.
If only one image file is given, and its name is the first in a sequence (e.g., as indicated by ending in '.001'), subsequent image segments will be included automatically.

.SH AUTHOR
Brian Carrier <carrier at sleuthkit dot org>

Send documentation updates to <doc-updates at sleuthkit dot org>
Something went wrong with that request. Please try again.