From: LDB <thesource@ldb-jab.org>
To: Nicle <ynicle@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: How to lseek the larger file > 2GB under linux
Date: Sun, 17 May 2009 14:10:50 -0400 [thread overview]
Message-ID: <4A10532A.60500@master.ldb-jab.org> (raw)
In-Reply-To: <d13fb4990905170842l5f700842k43db34f44ef2f829@mail.gmail.com>
Nicle wrote:
> Hi all,
>
> I have a file > 2GB, and my job is seeking the file to pos: 2.1G.
> But, it seems that the lseek64 doesn't work.
> Here is the sample code:
>
> #define _LARGEFILE64_SOURCE
> #include ...
>
> int main()
> {
> int fd = -1;
> long long pos = (long long) 2*1024*1024*1024 + 10; // over 2G
>
> fd = open(FILENAME, O_WRONLY|O_LARGEFILE);
> if (fd < 0){
> ...
> }
>
> if (lseek64(fd, pos, SEEK_SET) < 0) {
> fprintf(stderr, "Failed seeking to %lld, %s\n", pos, strerror(errno));
> }
>
> return 0;
> }
>
> Then the building cmd:
> gcc -o test test.c -D_FILE_OFFSET_BITS=64
>
> Output:
> Failed seeking to 2147483658, Success.
>
> The return val of lseek64 was "<0", but the strerror told me "Success".
> --
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
I changed the below a little, but when I seeked to 2.1GB,
it worked fine. I am not writing like you, but reading.
#define _LARGEFILE64_SOURCE
#include <stdio.h>
#include <sys/types.h>
#include <unistd.h>
#include <stdlib.h>
#include <errno.h>
#include <string.h>
#include <sys/stat.h>
#include <fcntl.h>
int main()
{
int fd, ret;
size_t count = 200;
long long pos = (long long) 2*1024*1024*1024 + 10; // over 2G
char buf[count];
fd = open("/tmp/fish", O_RDONLY|O_LARGEFILE);
if (fd < 0){
fprintf(stderr, "%s\n", strerror(errno));
exit(1);
}
if (lseek64(fd, pos, SEEK_SET) < 0) {
fprintf(stderr, "Failed seeking to %lld, %s\n", pos, strerror(errno));
exit(1);
}
if ((ret = read(fd, buf, count)) < 0) {
fprintf(stderr, "Failed reading: %s\n", strerror(errno));
exit(1);
}
buf[ret] = 0x00;
printf("%s\n", buf);
close(fd);
return 0;
}
next prev parent reply other threads:[~2009-05-17 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d13fb4990905170840j6ac84b0ej758582e5ffb5fa8c@mail.gmail.com>
2009-05-17 15:42 ` How to lseek the larger file > 2GB under linux Nicle
2009-05-17 16:20 ` Michal Nazarewicz
[not found] ` <d13fb4990905172137l1a4a9c92k47988da28ad4b7b1@mail.gmail.com>
2009-05-18 4:38 ` Nicle
2009-05-17 18:10 ` LDB [this message]
2009-05-17 20:09 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A10532A.60500@master.ldb-jab.org \
--to=thesource@ldb-jab.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=ynicle@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).