https://github.com/torvalds/linux
Revision fbbf69456619de5d251cb9f1df609069178c62d5 authored by Eric Sandeen on 03 October 2009, 01:20:55 UTC, committed by Theodore Ts'o on 03 October 2009, 01:20:55 UTC
On a 256M filesystem, doing this in a loop:

        xfs_io -F -f -d -c 'pwrite 0 64m' test
        rm -f test

eventually leads to ENOSPC.  (the xfs_io command does a
64m direct IO write to the file "test")

As with other block allocation callers, it looks like we need to
potentially retry the allocations on the initial ENOSPC.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
1 parent 74072d0
History
Tip revision: fbbf69456619de5d251cb9f1df609069178c62d5 authored by Eric Sandeen on 03 October 2009, 01:20:55 UTC
[PATCH] ext4: retry failed direct IO allocations
Tip revision: fbbf694
File Mode Size
Documentation
arch
block
crypto
drivers
firmware
fs
include
init
ipc
kernel
lib
mm
net
samples
scripts
security
sound
tools
usr
virt
.gitignore -rw-r--r-- 952 bytes
.mailmap -rw-r--r-- 3.9 KB
COPYING -rw-r--r-- 18.3 KB
CREDITS -rw-r--r-- 91.8 KB
Kbuild -rw-r--r-- 2.4 KB
MAINTAINERS -rw-r--r-- 153.5 KB
Makefile -rw-r--r-- 55.4 KB
README -rw-r--r-- 17.0 KB
REPORTING-BUGS -rw-r--r-- 3.3 KB

README

back to top