From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 105121] New: lseek() hangs for a long time on allocated files
Date: Mon, 28 Sep 2015 12:27:05 +0000 [thread overview]
Message-ID: <bug-105121-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=105121
Bug ID: 105121
Summary: lseek() hangs for a long time on allocated files
Product: File System
Version: 2.5
Kernel Version: 4.2.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: iam@valdikss.org.ru
Regression: No
Created attachment 188751
--> https://bugzilla.kernel.org/attachment.cgi?id=188751&action=edit
lseek test program
lseek() call hangs for a long time on fallocate allocated files on ext4.
Steps to reproduce:
1. gcc -o prog lseek-fallocate.c
2. fallocate -l 1G test
3. cat test > /dev/null
4. ./prog
Actual result:
prog hangs for 2 minutes on my system while doing lseek().
Expected result:
lseek() instantly return ENXIO.
Usually lseek works much faster if file wasn't cat'ed before lseek.
Works properly on btrfs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-09-28 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 12:27 bugzilla-daemon [this message]
2015-09-28 14:37 ` [Bug 105121] lseek(SEEK_DATA) hangs for a long time for sparse files in the page cache bugzilla-daemon
2015-09-28 14:47 ` bugzilla-daemon
2015-09-28 14:52 ` bugzilla-daemon
2015-09-28 15:15 ` bugzilla-daemon
2015-09-28 15:23 ` bugzilla-daemon
2019-01-18 7:44 ` bugzilla-daemon
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=bug-105121-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).