diff options
| author | Lukas Czerner <lczerner@redhat.com> | 2012-03-20 03:07:43 (GMT) |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2012-03-20 03:07:43 (GMT) |
| commit | dc1841d6cff22b98deef46bfe768a9c678d917c2 (patch) | |
| tree | 2d97eb9fd90fcd42bee4f5d7b7d9adb2459983f6 /fs | |
| parent | 7877191c28b1e140795c0c951dde8aad43757378 (diff) | |
| download | linux-dc1841d6cff22b98deef46bfe768a9c678d917c2.tar.xz | |
ext4: give more helpful error message in ext4_ext_rm_leaf()
The error message produced by the ext4_ext_rm_leaf() when we are
removing blocks which accidentally ends up inside the existing extent,
is not very helpful, because we would like to also know which extent did
we collide with.
This commit changes the error message to get us also the information
about the extent we are colliding with.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/ext4/extents.c | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index 9ac89b6..5c9c067 100644 --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -2366,8 +2366,11 @@ ext4_ext_rm_leaf(handle_t *handle, struct inode *inode, ex_ee_len = ext4_ext_get_actual_len(ex); continue; } else if (b != ex_ee_block + ex_ee_len - 1) { - EXT4_ERROR_INODE(inode," bad truncate %u:%u\n", - start, end); + EXT4_ERROR_INODE(inode, + "can not handle truncate %u:%u " + "on extent %u:%u", + start, end, ex_ee_block, + ex_ee_block + ex_ee_len - 1); err = -EIO; goto out; } else if (a != ex_ee_block) { |