]> git.ipfire.org Git - thirdparty/util-linux.git/blob - disk-utils/isosize.8
Merge branch 'meson-more-build-options' of https://github.com/jwillikers/util-linux
[thirdparty/util-linux.git] / disk-utils / isosize.8
1 .TH ISOSIZE 8 "June 2011" "util-linux" "System Administration"
2 .SH NAME
3 isosize \- output the length of an iso9660 filesystem
4 .SH SYNOPSIS
5 .B isosize
6 .RI [options] " iso9660_image_file"
7 .SH DESCRIPTION
8 .PP
9 This command outputs the length of an iso9660 filesystem that
10 is contained in the specified file. This file may be a normal file or
11 a block device (e.g.\& /dev/hdd or /dev/sr0). In the absence of
12 any options (and errors), it will output the size of the iso9660
13 filesystem in bytes. This can now be a large number (>> 4\ GB).
14 .SH OPTIONS
15 .TP
16 .BR \-x , " \-\-sectors"
17 Show the block count and block size in human-readable form.
18 The output uses the term "sectors" for "blocks".
19 .TP
20 .BR \-d , " \-\-divisor " \fInumber\fR
21 Only has an effect when
22 .B \-x
23 is not given. The value shown (if no errors)
24 is the iso9660 file size in bytes divided by
25 .IR number .
26 So if
27 .I number
28 is the block size then the shown value will be the block count.
29 .PP
30 The size of the file (or block device) holding an iso9660
31 filesystem can be marginally larger than the actual size of the
32 iso9660 filesystem. One reason for this is that cd writers
33 are allowed to add "run out" sectors at the end of an iso9660
34 image.
35 .SH "EXIT STATUS"
36 .RS
37 .PD 0
38 .TP
39 .B 0
40 success
41 .TP
42 .B 1
43 generic failure, such as invalid usage
44 .TP
45 .B 32
46 all failed
47 .TP
48 .B 64
49 some failed
50 .PD
51 .RE
52 .SH AVAILABILITY
53 The isosize command is part of the util-linux package and is available from
54 .UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
55 Linux Kernel Archive
56 .UE .