diff options
| author | Eric Sandeen <sandeen@redhat.com> | 2009-10-02 21:20:55 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2009-10-02 21:20:55 -0400 |
| commit | fbbf69456619de5d251cb9f1df609069178c62d5 (patch) | |
| tree | e0a5bc75a02dda7f46ba4d0e838c54f39b1fe4f6 /crypto | |
| parent | 74072d0a63553720dd3c70a8b8e9407eb2027dbe (diff) | |
| download | linux-3.10-fbbf69456619de5d251cb9f1df609069178c62d5.tar.gz linux-3.10-fbbf69456619de5d251cb9f1df609069178c62d5.tar.bz2 linux-3.10-fbbf69456619de5d251cb9f1df609069178c62d5.zip | |
[PATCH] ext4: retry failed direct IO allocations
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>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions