2 .\" Copyright (c) 1980, 1991 Regents of the University of California.
3 .\" and Copyright (c) 2011, Michael Kerrisk <mtk.manpages@gmail.com>
4 .\" All rights reserved.
6 .\" %%%LICENSE_START(BSD_4_CLAUSE_UCB)
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" @(#)lseek.2 6.5 (Berkeley) 3/10/91
38 .\" Modified 1993-07-23 by Rik Faith <faith@cs.unc.edu>
39 .\" Modified 1995-06-10 by Andries Brouwer <aeb@cwi.nl>
40 .\" Modified 1996-10-31 by Eric S. Raymond <esr@thyrsus.com>
41 .\" Modified 1998-01-17 by Michael Haardt
42 .\" <michael@cantor.informatik.rwth-aachen.de>
43 .\" Modified 2001-09-24 by Michael Haardt <michael@moria.de>
44 .\" Modified 2003-08-21 by Andries Brouwer <aeb@cwi.nl>
45 .\" 2011-09-18, mtk, Added SEEK_DATA + SEEK_HOLE
47 .TH LSEEK 2 2016-03-15 "Linux" "Linux Programmer's Manual"
49 lseek \- reposition read/write file offset
51 .B #include <sys/types.h>
53 .B #include <unistd.h>
55 .BI "off_t lseek(int " fd ", off_t " offset ", int " whence );
59 function repositions the file offset of the open file description
60 associated with the file descriptor
64 according to the directive
69 The file offset is set to
74 The file offset is set to its current location plus
79 The file offset is set to the size of the file plus
85 function allows the file offset to be set beyond the end
86 of the file (but this does not change the size of the file).
87 If data is later written at this point, subsequent reads of the data
88 in the gap (a "hole") return null bytes (\(aq\\0\(aq) until
89 data is actually written into the gap.
90 .SS Seeking file data and holes
91 Since version 3.1, Linux supports the following additional values for
95 Adjust the file offset to the next location
96 in the file greater than or equal to
102 then the file offset is set to
106 Adjust the file offset to the next hole in the file
107 greater than or equal to
111 points into the middle of a hole,
112 then the file offset is set to
114 If there is no hole past
116 then the file offset is adjusted to the end of the file
117 (i.e., there is an implicit hole at the end of any file).
119 In both of the above cases,
123 points past the end of the file.
125 These operations allow applications to map holes in a sparsely
127 This can be useful for applications such as file backup tools,
128 which can save space when creating backups and preserve holes,
129 if they have a mechanism for discovering holes.
131 For the purposes of these operations, a hole is a sequence of zeros that
132 (normally) has not been allocated in the underlying file storage.
133 However, a filesystem is not obliged to report holes,
134 so these operations are not a guaranteed mechanism for
135 mapping the storage space actually allocated to a file.
136 (Furthermore, a sequence of zeros that actually has been written
137 to the underlying storage may not be reported as a hole.)
138 In the simplest implementation,
139 a filesystem can support the operations by making
141 always return the offset of the end of the file,
146 (i.e., even if the location referred to by
149 it can be considered to consist of data that is a sequence of zeros).
150 .\" https://lkml.org/lkml/2011/4/22/79
151 .\" http://lwn.net/Articles/440255/
152 .\" http://blogs.oracle.com/bonwick/entry/seek_hole_and_seek_data
156 feature test macro must be defined in order to obtain the definitions of
167 operations are supported for the following filesystems:
169 Btrfs (since Linux 3.1)
171 OCFS (since Linux 3.2)
172 .\" commit 93862d5e1ab875664c6cc95254fc365028a48bb1
174 XFS (since Linux 3.5)
176 ext4 (since Linux 3.8)
178 tmpfs (since Linux 3.8)
180 NFS (since Linux 3.18)
181 .\" commit 1c6dcbe5ceff81c2cf8d929646af675cd59fe7c0
182 .\" commit 24bab491220faa446d945624086d838af41d616c
184 FUSE (since Linux 4.5)
185 .\" commit 0b5da8db145bfd44266ac964a2636a0cf8d7c286
187 Upon successful completion,
189 returns the resulting offset location as measured in bytes from the
190 beginning of the file.
191 On error, the value \fI(off_t)\ \-1\fP is returned and
193 is set to indicate the error.
198 is not an open file descriptor.
203 Or: the resulting file offset would be negative,
204 or beyond the end of a seekable device.
205 .\" Some systems may allow negative offsets for character devices
206 .\" and/or for remote filesystems.
209 .\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
210 The resulting file offset cannot be represented in an
215 is associated with a pipe, socket, or FIFO.
223 and the file offset is beyond the end of the file.
225 POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD.
230 are nonstandard extensions also present in Solaris,
231 FreeBSD, and DragonFly BSD;
232 they are proposed for inclusion in the next POSIX revision (Issue 8).
233 .\" FIXME . Review http://austingroupbugs.net/view.php?id=415 in the future
237 for a discussion of the relationship between file descriptors,
238 open file descriptions, and files.
240 Some devices are incapable of seeking and POSIX does not specify which
246 on a terminal device returns
248 .\" Other systems return the number of written characters,
249 .\" using SEEK_SET to set the counter. (Of written characters.)
251 When converting old code, substitute values for \fIwhence\fP with the
265 .\" SVr1-3 returns \fIlong\fP instead of \fIoff_t\fP,
266 .\" (ancient) BSD returns \fIint\fP.
268 Note that file descriptors created by
272 refer to the same open file descriptions (and thus file offsets),
273 so seeking on such files may be subject to race conditions.
280 .BR posix_fallocate (3)