aboutsummaryrefslogtreecommitdiffstats
path: root/fs/jbd2/checkpoint.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2011-08-04 10:52:27 -0400
committerChris Mason <chris.mason@oracle.com>2011-08-16 21:09:15 -0400
commitd5e2003c2bcda93a8f2e668eb4642d70c9c38301 (patch)
tree336234b9d9a144f180bc51738f55fef7f743b725 /fs/jbd2/checkpoint.c
parent2ab1ba68aeaecd41c4b34f0eaf1d70a37367fb1a (diff)
Btrfs: detect wether a device supports discard
We have a problem where if a user specifies discard but doesn't actually support it we will return EOPNOTSUPP from btrfs_discard_extent. This is a problem because this gets called (in a fashion) from the tree log recovery code, which has a nice little BUG_ON(ret) after it, which causes us to fail the tree log replay. So instead detect wether our devices support discard when we're adding them and then don't issue discards if we know that the device doesn't support it. And just for good measure set ret = 0 in btrfs_issue_discard just in case we still get EOPNOTSUPP so we don't screw anybody up like this again. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/jbd2/checkpoint.c')
0 files changed, 0 insertions, 0 deletions