1 .\" Copyright (c) 1980, 1991 Regents of the University of California.
2 .\" and Copyright (c) 2011, Michael Kerrisk <mtk.manpages@gmail.com>
3 .\" All rights reserved.
5 .\" SPDX-License-Identifier: BSD-4-Clause-UC
7 .\" @(#)lseek.2 6.5 (Berkeley) 3/10/91
9 .\" Modified 1993-07-23 by Rik Faith <faith@cs.unc.edu>
10 .\" Modified 1995-06-10 by Andries Brouwer <aeb@cwi.nl>
11 .\" Modified 1996-10-31 by Eric S. Raymond <esr@thyrsus.com>
12 .\" Modified 1998-01-17 by Michael Haardt
13 .\" <michael@cantor.informatik.rwth-aachen.de>
14 .\" Modified 2001-09-24 by Michael Haardt <michael@moria.de>
15 .\" Modified 2003-08-21 by Andries Brouwer <aeb@cwi.nl>
16 .\" 2011-09-18, mtk, Added SEEK_DATA + SEEK_HOLE
18 .TH LSEEK 2 2022-09-09 "Linux man-pages (unreleased)"
20 lseek \- reposition read/write file offset
23 .RI ( libc ", " \-lc )
26 .B #include <unistd.h>
28 .BI "off_t lseek(int " fd ", off_t " offset ", int " whence );
32 repositions the file offset of the open file description
33 associated with the file descriptor
37 according to the directive
42 The file offset is set to
47 The file offset is set to its current location plus
52 The file offset is set to the size of the file plus
57 allows the file offset to be set beyond the end
58 of the file (but this does not change the size of the file).
59 If data is later written at this point, subsequent reads of the data
60 in the gap (a "hole") return null bytes (\(aq\e0\(aq) until
61 data is actually written into the gap.
62 .SS Seeking file data and holes
63 Since version 3.1, Linux supports the following additional values for
67 Adjust the file offset to the next location
68 in the file greater than or equal to
74 then the file offset is set to
78 Adjust the file offset to the next hole in the file
79 greater than or equal to
83 points into the middle of a hole,
84 then the file offset is set to
86 If there is no hole past
88 then the file offset is adjusted to the end of the file
89 (i.e., there is an implicit hole at the end of any file).
91 In both of the above cases,
95 points past the end of the file.
97 These operations allow applications to map holes in a sparsely
99 This can be useful for applications such as file backup tools,
100 which can save space when creating backups and preserve holes,
101 if they have a mechanism for discovering holes.
103 For the purposes of these operations, a hole is a sequence of zeros that
104 (normally) has not been allocated in the underlying file storage.
105 However, a filesystem is not obliged to report holes,
106 so these operations are not a guaranteed mechanism for
107 mapping the storage space actually allocated to a file.
108 (Furthermore, a sequence of zeros that actually has been written
109 to the underlying storage may not be reported as a hole.)
110 In the simplest implementation,
111 a filesystem can support the operations by making
113 always return the offset of the end of the file,
118 (i.e., even if the location referred to by
121 it can be considered to consist of data that is a sequence of zeros).
122 .\" https://lkml.org/lkml/2011/4/22/79
123 .\" http://lwn.net/Articles/440255/
124 .\" http://blogs.oracle.com/bonwick/entry/seek_hole_and_seek_data
128 feature test macro must be defined in order to obtain the definitions of
139 operations are supported for the following filesystems:
141 Btrfs (since Linux 3.1)
143 OCFS (since Linux 3.2)
144 .\" commit 93862d5e1ab875664c6cc95254fc365028a48bb1
146 XFS (since Linux 3.5)
148 ext4 (since Linux 3.8)
153 NFS (since Linux 3.18)
154 .\" commit 1c6dcbe5ceff81c2cf8d929646af675cd59fe7c0
155 .\" commit 24bab491220faa446d945624086d838af41d616c
157 FUSE (since Linux 4.5)
158 .\" commit 0b5da8db145bfd44266ac964a2636a0cf8d7c286
160 GFS2 (since Linux 4.15)
161 .\" commit 3a27411cb4bc3ce31db228e3569ad01b462a4310
163 Upon successful completion,
165 returns the resulting offset location as measured in bytes from the
166 beginning of the file.
167 On error, the value \fI(off_t)\ \-1\fP is returned and
169 is set to indicate the error.
174 is not an open file descriptor.
179 Or: the resulting file offset would be negative,
180 or beyond the end of a seekable device.
181 .\" Some systems may allow negative offsets for character devices
182 .\" and/or for remote filesystems.
192 is beyond the end of the file, or
198 is within a hole at the end of the file.
201 .\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
202 The resulting file offset cannot be represented in an
207 is associated with a pipe, socket, or FIFO.
209 POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD.
214 are nonstandard extensions also present in Solaris,
215 FreeBSD, and DragonFly BSD;
216 they are proposed for inclusion in the next POSIX revision (Issue 8).
217 .\" FIXME . Review http://austingroupbugs.net/view.php?id=415 in the future
221 for a discussion of the relationship between file descriptors,
222 open file descriptions, and files.
226 file status flag is set on the open file description,
230 moves the file offset to the end of the file, regardless of the use of
235 data type is a signed integer data type specified by POSIX.1.
237 Some devices are incapable of seeking and POSIX does not specify which
243 on a terminal device fails with the error
245 .\" Other systems return the number of written characters,
246 .\" using SEEK_SET to set the counter. (Of written characters.)
254 .BR posix_fallocate (3)