aboutsummaryrefslogtreecommitdiffstats
path: root/cmds-filesystem.c
diff options
context:
space:
mode:
authorQu Wenruo <quwenruo@cn.fujitsu.com>2016-03-31 10:19:34 +0800
committerDavid Sterba <dsterba@suse.com>2016-05-02 14:40:05 +0200
commit12234d0202a30fb225ebae817b5eb2e80b641d4c (patch)
tree18caf1953fbff72e274ec0fdb8720e580f11fd7e /cmds-filesystem.c
parent1a9df1c68b1e2f479d6b73e96951ca708740c3f9 (diff)
downloadbtrfs-progs-12234d0202a30fb225ebae817b5eb2e80b641d4c.tar.gz
btrfs-progs-12234d0202a30fb225ebae817b5eb2e80b641d4c.tar.xz
btrfs-progs-12234d0202a30fb225ebae817b5eb2e80b641d4c.zip
btrfs-progs: fsck: Fix a false metadata extent warning
At least 2 user from mail list reported btrfsck reported false alert of "bad metadata [XXXX,YYYY) crossing stripe boundary". While the reported number are all inside the same 64K boundary. After some check, all the false alert have the same bytenr feature, which can be divided by stripe size (64K). The result seems to be initial 'max_size' can be 0, causing 'start' + 'max_size' - 1, to cross the stripe boundary. Fix it by always update extent_record->cross_stripe when the extent_record is updated, to avoid temporary false alert to be reported. Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'cmds-filesystem.c')
0 files changed, 0 insertions, 0 deletions