linux.git/fs/bcachefs/alloc_foreground.c, branch v6.8 Linux kernel source tree bcachefs: helpers for printing data types 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-07T01:57:43+00:00 e58f963cecbdb08f28334122afba93a7840beabc We need bounds checking since new versions may introduce new data types. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
We need bounds checking since new versions may introduce new data types.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: btree_iter -> btree_path_idx_t 2024-01-01T16:47:43+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-04T05:39:38+00:00 07f383c71fadc952059ed4ffe37dd465bda4ad3e Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: for_each_member_device_rcu() now declares loop iter 2024-01-01T16:47:42+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-17T07:34:05+00:00 41b84fb489f7707af4490d1e5e22d88f3207da71 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: use track_event_change() for allocator blocked stats 2024-01-01T16:47:42+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-11T15:15:18+00:00 6d5c606c1cdc4e7c3d2ca83660e9f68827fc04ed Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: simplify bch_devs_list 2024-01-01T16:47:42+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-24T02:02:45+00:00 037a2d9f48285bf3bfed0f55f1aee04d8b329d07 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix open coded set_btree_iter_dontneed() 2024-01-01T16:47:40+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-06T22:53:59+00:00 a0acc24fedbe067b30f4320daa8d63b404f6ccd9 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: ONLY_SPECIFIED_DEVS doesn't mean ignore durability anymore 2024-01-01T16:47:39+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-29T00:47:26+00:00 48dade81760ed551898ec20f59ace7ac2f5620b3 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix bch2_alloc_sectors_start_trans() error handling 2023-12-20T00:01:52+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-19T22:16:34+00:00 247ce5f1bb3ea90879e8552b8edf4885b9a9f849 When we fail to allocate because of insufficient open buckets, we don't want to retry from the full set of devices - we just want to retry in blocking mode. But if the retry in blocking mode fails with a different error code, we end up squashing the -BCH_ERR_open_buckets_empty error with an error that makes us thing we won't be able to allocate (insufficient_devices) - which is incorrect when we didn't try to allocate from the full set of devices, and causes the write to fail. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
When we fail to allocate because of insufficient open buckets, we don't
want to retry from the full set of devices - we just want to retry in
blocking mode.

But if the retry in blocking mode fails with a different error code, we
end up squashing the -BCH_ERR_open_buckets_empty error with an error
that makes us thing we won't be able to allocate (insufficient_devices)
- which is incorrect when we didn't try to allocate from the full set of
devices, and causes the write to fail.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: deallocate_extra_replicas() 2023-11-24T08:03:47+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-20T23:23:26+00:00 0af8a06a4ce823e380385cdd9538cdd968a1ffae When allocating from devices with different durability, we might end up with more replicas than required; this changes bch2_alloc_sectors_start() to check for this, and drop replicas that aren't needed to hit the number of replicas requested. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
When allocating from devices with different durability, we might end up
with more replicas than required; this changes
bch2_alloc_sectors_start() to check for this, and drop replicas that
aren't needed to hit the number of replicas requested.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Put erasure coding behind an EXPERIMENTAL kconfig option 2023-11-24T05:29:58+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-23T22:56:14+00:00 6201d91ee32cf92e9bcca69a3cf73461827b5ce5 We still have disk space accounting changes coming for erasure coding, and the changes won't be as strictly backwards compatible as they'd ought to be - specifically, we need to start accounting striped data under a separate counter in bch_alloc (which describes buckets). A fsck will suffice for upgrading/downgrading, but since erasure coding is the most incomplete major feature of bcachefs it still makes sense to put behind a separate kconfig option, so that users are fully aware. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
We still have disk space accounting changes coming for erasure coding,
and the changes won't be as strictly backwards compatible as they'd
ought to be - specifically, we need to start accounting striped data
under a separate counter in bch_alloc (which describes buckets).

A fsck will suffice for upgrading/downgrading, but since erasure coding
is the most incomplete major feature of bcachefs it still makes sense to
put behind a separate kconfig option, so that users are fully aware.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>