Actions
Feature #3826
closeduclient: Be more aggressive about checking for pools we can't write to
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Client
Labels (FS):
Pull request ID:
Description
Right now the client will happily buffer up writes to a pool that it can't actually write to. #2753 is going to make sure this responds with EPERM on fsync or close (if it knows by then), but we should be more polite about returning that failure earlier on.
Updated by Greg Farnum almost 9 years ago
- Status changed from New to Resolved
Zheng did this a few months ago; we now write to a test object in every newly-seen pool.
Actions