February 3, 2021 4:56 PM, "Qu Wenruo" wrote:
> On 2021/2/4 上午5:54, jos...@mailmag.net wrote:
>
>> Good Evening.
>>
>> I have a large BTRFS array, (14 Drives, ~100 TB RAW) which has been having
>> problems mounting on
>> boot without timing out. This causes the system to drop to emergency mode.
On Wed, Feb 3, 2021 at 10:16 PM Erik Jensen wrote:
> On Sun, Jan 31, 2021 at 9:50 PM Su Yue wrote:
> > On Mon 01 Feb 2021 at 10:35, Qu Wenruo
> > wrote:
> > > On 2021/1/29 下午2:39, Erik Jensen wrote:
> > >> On Mon, Jan 25, 2021 at 8:54 PM Erik Jensen
> > >> wrote:
> > >>> On Wed, Jan 20, 2021 at
On Fri, Feb 5, 2021 at 12:55 PM Naohiro Aota wrote:
>
> On Fri, Feb 05, 2021 at 11:49:05AM +, Filipe Manana wrote:
> > On Fri, Feb 5, 2021 at 9:26 AM Naohiro Aota wrote:
> > >
> > > Since the zoned filesystem requires sequential write out of metadata, we
> > > cannot proceed with a hole in tr
From: Filipe Manana
When creating a snapshot we check if the current number of swap files, in
the root, is non-zero, and if it is, we error out and warn that we can not
create the snapshot because there are active swap files.
However this is racy because when a task started activation of a swap
From: Filipe Manana
The following patchset fixes 2 bugs with the swapfile support, where we can
end up falling back to COW when writing to an active swapfile. The first patch
is actually independent and just makes the nocow buffered IO path more efficient
by eliminating a repeated check for a rea
From: Filipe Manana
During the nocow writeback path, we currently iterate the rbtree of block
groups twice: once for checking if the target block group is RO with the
call to btrfs_extent_readonly()), and once again for getting a nocow
reference on the block group with a call to btrfs_inc_nocow_w
On Fri, Feb 5, 2021 at 7:44 AM Anand Jain wrote:
>
> On 2/4/2021 6:11 PM, Filipe Manana wrote:
> > On Thu, Feb 4, 2021 at 8:48 AM Anand Jain wrote:
> >>
> >> On 2/3/2021 7:17 PM, fdman...@kernel.org wrote:
> >>> From: Filipe Manana
> >>>
> >>> When we active a swap file, at btrfs_swap_activate()
Sehr geehrte(r) Herr / Frau,
operatingsystem.de Domain Name ist jetzt verfügbar und ist jetzt zu verkaufen.
Vielen Dank im Voraus.
Ein angenehmes Wochenende wünscht Ihnen
Marco Maier
..
On Fri, Feb 5, 2021 at 11:49 AM Filipe Manana wrote:
>
> On Fri, Feb 5, 2021 at 9:26 AM Naohiro Aota wrote:
> >
> > Since the zoned filesystem requires sequential write out of metadata, we
> > cannot proceed with a hole in tree-log pages. When such a hole exists,
> > btree_write_cache_pages() wil
> On Feb 5, 2021, at 1:58 AM, Boris Burkov wrote:
>
> On Thu, Feb 04, 2021 at 10:13:54PM -0800, Eric Biggers wrote:
>> On Thu, Feb 04, 2021 at 03:21:36PM -0800, Boris Burkov wrote:
>>> This patchset provides support for fsverity in btrfs.
>>
>> Very interested to see this! It generally looks g
> On Feb 5, 2021, at 3:06 AM, Nikolay Borisov wrote:
>
>> +
>> +/*
>> + * drop all the items for this inode with this key_type. Before
>> + * doing a verity enable we cleanup any existing verity items.
>> + *
>> + * This is also used to clean up if a verity enable failed half way
>> + * throug
On Fri, Feb 05, 2021 at 02:19:50PM +, Filipe Manana wrote:
> On Fri, Feb 5, 2021 at 11:49 AM Filipe Manana wrote:
> >
> > On Fri, Feb 5, 2021 at 9:26 AM Naohiro Aota wrote:
> > >
> > > Since the zoned filesystem requires sequential write out of metadata, we
> > > cannot proceed with a hole in
On Fri, Feb 5, 2021 at 2:58 PM Naohiro Aota wrote:
>
> Since the zoned filesystem requires sequential write out of metadata, we
> cannot proceed with a hole in tree-log pages. When such a hole exists,
> btree_write_cache_pages() will return -EAGAIN. This happens when someone,
> e.g., a concurrent
Since the zoned filesystem requires sequential write out of metadata, we
cannot proceed with a hole in tree-log pages. When such a hole exists,
btree_write_cache_pages() will return -EAGAIN. This happens when someone,
e.g., a concurrent transaction commit, writes a dirty extent in this
tree-log com
> On Feb 5, 2021, at 1:39 AM, Eric Biggers wrote:
>
> On Thu, Feb 04, 2021 at 03:21:38PM -0800, Boris Burkov wrote:
>> +/*
>> + * drop all the items for this inode with this key_type. Before
>> + * doing a verity enable we cleanup any existing verity items.
>> + *
>> + * This is also used to c
On 2/5/21 12:24 AM, Zygo Blaxell wrote:
On Mon, Feb 01, 2021 at 10:28:20PM +0100, Goffredo Baroncelli wrote:
From: Goffredo Baroncelli
[...]
Hi Zygo
Well, I guess if you're going to keep putting the mount option in each
new patch version, then I'm going to keep saying "please remove the
moun
On Fri, Feb 05, 2021 at 11:49:05AM +, Filipe Manana wrote:
> On Fri, Feb 5, 2021 at 9:26 AM Naohiro Aota wrote:
> >
> > Since the zoned filesystem requires sequential write out of metadata, we
> > cannot proceed with a hole in tree-log pages. When such a hole exists,
> > btree_write_cache_page
From: Filipe Manana
When we active a swap file, at btrfs_swap_activate(), we acquire the
exclusive operation lock to prevent the physical location of the swap
file extents to be changed by operations such as balance and device
replace/resize/remove. We also call there can_nocow_extent() which,
am
On Fri, Feb 5, 2021 at 9:26 AM Naohiro Aota wrote:
>
> Since the zoned filesystem requires sequential write out of metadata, we
> cannot proceed with a hole in tree-log pages. When such a hole exists,
> btree_write_cache_pages() will return -EAGAIN. We cannot wait for the range
> to be written, be
Hi,
btrfs-progs version 5.10.1 have been released.
The static build got broken due to libmount added in 5.10, this works now. The
minimum libmount version is 2.24 that is not available on some LTS distros like
CentOS 7. The plan is to bring the support back, reimplementing some libmount
functiona
On Fri, Feb 5, 2021 at 9:15 AM Naohiro Aota wrote:
>
> David, could you fold the below incremental diff to this patch? Or, I
> can send a full replacement patch.
>
> diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
> index 8be3164d4c5d..4e72794342c0 100644
> --- a/fs/btrfs/tree-log.c
> +++ b
Since the zoned filesystem requires sequential write out of metadata, we
cannot proceed with a hole in tree-log pages. When such a hole exists,
btree_write_cache_pages() will return -EAGAIN. We cannot wait for the range
to be written, because it will cause a deadlock. So, let's bail out to a
full c
David, could you fold the below incremental diff to this patch? Or, I
can send a full replacement patch.
diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
index 8be3164d4c5d..4e72794342c0 100644
--- a/fs/btrfs/tree-log.c
+++ b/fs/btrfs/tree-log.c
@@ -143,6 +143,7 @@ static int start_log_trans
On 5.02.21 г. 1:21 ч., Boris Burkov wrote:
> From: Chris Mason
>
> Add support for fsverity in btrfs. To support the generic interface in
> fs/verity, we add two new item types in the fs tree for inodes with
> verity enabled. One stores the per-file verity descriptor and the other
> stores the
24 matches
Mail list logo
