At 03/08/2017 02:47 PM, Adam Borowski wrote:
On Wed, Mar 08, 2017 at 10:41:17AM +0800, Qu Wenruo wrote:
This patchset will introduce a new per-chunk degradable check for
btrfs, allow above case to succeed, and it's quite small anyway.
v3:
Remove one duplicated missing device output
Use the advice from Anand Jain, not to add new members in btrfs_device,
but use a new structure extra_rw_degrade_errors, to record error when
sending down/waiting device.
Sorry Dmitrii Tcvetkov and Adam Borowski, I'm afraid I can't add your
tested-by tags in v3, as the 4th and 4th patches have quite a big change,
so you may need to retest the new patchset.
Well, testing stuff is why we're here :)
Re-tested, as far as your patch goes all is well.
Looks like I found an unrelated bug, though, that messed with my testing.
And it looks like a nasty one: once "btrfs dev scan" sees a disk, it stores
its device and will then happily use it without verification even if it's
been pulled out and replaced by something else. Lemme investigate that
later today.
It would be nice if you can send detailed info to mail list.
AFAIK, btrfs will check its superblock for devid and device UUID, to
ensure that's the device we're using.
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
