do not open the extend inode reference at the beginning
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Btrfs: set the INCOMPAT_EXTENDED_IREF when the extended iref is insertedfs/ | +9 | 0 replies | |
| 2/2 | Btrfs: introduce noextiref mount optionfs/ fs/ fs/ +1 more | +51 | 10 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] do not open the extend inode reference at the beginning
In most cases, we do not insert so many inode references, so it is better that we don't set incompat flag -- EXTEND_IREF -- when we make a fs. Otherwise we can not mount the fs on the old kernel though there is no extend iref in fact.
And some users may not hope to inserting the extend inode reference because of the incompatible problem. In this case, we introduce a mount option named noextiref.
Note, if the extend inode reference function is enabled, we will fail to mount a fs with this option because there might be some extend irefs in the fs, we should not close this function.
This patchset is against:
[PATCH 1/2] Btrfs: fix unblocked autodefraggers when remount
[PATCH 2/2] Btrfs: use a lock to protect incompat/compat flag of the super block
Miao Xie (2):
Btrfs: set the INCOMPAT_EXTENDED_IREF when the extended iref is inserted
Btrfs: introduce noextiref mount option
fs/btrfs/ctree.h | 1 + fs/btrfs/disk-io.c | 9 +++++++++ fs/btrfs/inode-item.c | 20 ++++++++++---------- fs/btrfs/super.c | 41 ++++++++++++++++++++++++++++++++++++++++- 4 files changed, 60 insertions(+), 11 deletions(-)
Signature · 1 line
1.8.0.1