]> git.ipfire.org Git - thirdparty/util-linux.git/blame - disk-utils/isosize.8.adoc
Asciidoc: Fix artifact from initial import, sixth attempt
[thirdparty/util-linux.git] / disk-utils / isosize.8.adoc
CommitLineData
295b3979 1//po4a: entry man manual
c6a568fc
MB
2= isosize(8)
3:doctype: manpage
4:man manual: System Administration
5:man source: util-linux {release-version}
6:page-layout: base
7:command: isosize
8
9== NAME
10
11isosize - output the length of an iso9660 filesystem
12
13== SYNOPSIS
14
4d297435 15*isosize* [options] _iso9660_image_file_
c6a568fc
MB
16
17== DESCRIPTION
18
ab3e786d 19This command outputs the length of an iso9660 filesystem that is contained in the specified file. This file may be a normal file or a block device (e.g. _/dev/hdd_ or _/dev/sr0_). In the absence of any options (and errors), it will output the size of the iso9660 filesystem in bytes. This can now be a large number (>> 4 GB).
c6a568fc
MB
20
21== OPTIONS
22
23*-x*, *--sectors*::
299604dd 24Show the block count and block size in human-readable form. The output uses the term "sectors" for "blocks".
c6a568fc
MB
25
26*-d*, *--divisor* _number_::
299604dd
MB
27Only has an effect when *-x* is not given. The value shown (if no errors) is the iso9660 file size in bytes divided by _number_. So if _number_ is the block size then the shown value will be the block count.
28+
c6a568fc
MB
29The size of the file (or block device) holding an iso9660 filesystem can be marginally larger than the actual size of the iso9660 filesystem. One reason for this is that cd writers are allowed to add "run out" sectors at the end of an iso9660 image.
30
31== EXIT STATUS
32
c6a568fc 33*0*::
299604dd 34success
c6a568fc 35*1*::
299604dd 36generic failure, such as invalid usage
c6a568fc 37*32*::
299604dd 38all failed
c6a568fc 39*64*::
299604dd 40some failed
c6a568fc
MB
41
42include::../man-common/bugreports.adoc[]
43
44include::../man-common/footer.adoc[]
45
46ifdef::translation[]
47include::../man-common/translation.adoc[]
48endif::[]