Date: Mon, 19 Aug 2002 15:00:10 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/41792: lseek after ftruncate fails Message-ID: <200208192200.g7JM0Al2075323@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR misc/41792; it has been noted by GNATS.
From: Bruce Evans <bde@zeta.org.au>
To: Yury Izrailevsky <izrailev@yahoo.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/41792: lseek after ftruncate fails
Date: Tue, 20 Aug 2002 07:58:51 +1000 (EST)
On Mon, 19 Aug 2002, Yury Izrailevsky wrote:
> >Description:
> File operation problem. Running the following:
>
> write(fd, buffer, 8K);
> ftruncate(fd, 0);
> write(fd, buffer, 1);
> off = lseek(fd, 0, SEEK_END);
> printf("%d", off);
>
> Output: 24576, expected: 1.
>
> The size of the actual file is 1 (if you ls -l on it). However, lseek goes way past it...
>
> Noticed this while running connectathon rewind test (part of special test suite). But fails even if don't go over NFS but just run on the local file system.
>
> I suspect the problem is with the FS cache. Or perhaps lseek and/or ftruncate are just broken...
This only fails over nfs under -current. stat(2) and thus ls(1) shows that
the file size is 24576 until the next read(2) of the file. Then the size
becomes 1.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208192200.g7JM0Al2075323>