mirror of
git://sourceware.org/git/lvm2.git
synced 2025-01-03 05:18:29 +03:00
thin: add comment with future extension
It could be actually better to use even cache origin in read-only mode so there could no be some 'acidental' change being done on this volume. This however need further tools enhancment - where we would need to handle whole subtree on 'lvchange -pr/-prw'.
This commit is contained in:
parent
75f2388093
commit
79121416df
@ -99,6 +99,10 @@ int attach_thin_external_origin(struct lv_segment *seg,
|
||||
external_lv->name);
|
||||
external_lv->status &= ~LVM_WRITE;
|
||||
}
|
||||
|
||||
// TODO: should we mark even origin read-only ?
|
||||
//if (lv_is_cache(external_lv)) /* read-only corigin of cache LV */
|
||||
// seg_lv(first_seg(external_lv), 0)->status &= ~LVM_WRITE;
|
||||
}
|
||||
|
||||
return 1;
|
||||
|
Loading…
Reference in New Issue
Block a user