On Tue, Feb 2, 2021 at 6:35 PM Steven Whitehouse
wrote:
> Hi,
> On 24/01/2021 06:44, Abhijith Das wrote:
>
> Hi all,
>
> I've been looking at rgrp.c:gfs2_alloc_blocks(), which is called from
> various places to allocate single/multiple blocks for inodes. I've come up
> with some data structures
- Original Message -
> On Thu, Feb 25, 2021 at 7:48 PM Bob Peterson wrote:
>
> > - Original Message -
> > > >> once we change the journal format, in addition to recording block
> > numbers
> > > >> as extents, there are some additional issues we should address at the
> > same
> >
On Thu, Feb 25, 2021 at 7:48 PM Bob Peterson wrote:
> - Original Message -
> > >> once we change the journal format, in addition to recording block
> numbers
> > >> as extents, there are some additional issues we should address at the
> same
> > >> time:
>
> One thing I've always thought
- Original Message -
> >> once we change the journal format, in addition to recording block numbers
> >> as extents, there are some additional issues we should address at the same
> >> time:
One thing I've always thought we should improve upon was the way we manage
our bitmaps. Right now,
On Mon, Feb 22, 2021 at 12:41 PM Andreas Gruenbacher
wrote:
> On Mon, Feb 22, 2021 at 11:21 AM Steven Whitehouse
> wrote:
>
>> Hi,
>> On 20/02/2021 09:48, Andreas Gruenbacher wrote:
>>
>> Hi all,
>>
>> once we change the journal format, in addition to recording block numbers
>> as extents,
On Mon, Feb 22, 2021 at 11:21 AM Steven Whitehouse
wrote:
> Hi,
> On 20/02/2021 09:48, Andreas Gruenbacher wrote:
>
> Hi all,
>
> once we change the journal format, in addition to recording block numbers
> as extents, there are some additional issues we should address at the same
> time:
>
> I.
Hi,
On 20/02/2021 09:48, Andreas Gruenbacher wrote:
Hi all,
once we change the journal format, in addition to recording block
numbers as extents, there are some additional issues we should address
at the same time:
I. The current transaction format of our journals is as follows:
* One
Hi all,
once we change the journal format, in addition to recording block numbers
as extents, there are some additional issues we should address at the same
time:
I. The current transaction format of our journals is as follows:
- One METADATA log descriptor block for each [503 / 247 / 119 /
Hi,
On 24/01/2021 06:44, Abhijith Das wrote:
Hi all,
I've been looking at rgrp.c:gfs2_alloc_blocks(), which is called from
various places to allocate single/multiple blocks for inodes. I've
come up with some data structures to accomplish recording of these
allocations as extents.
I'm
- Original Message -
> Hi all,
>
> I've been looking at rgrp.c:gfs2_alloc_blocks(), which is called from
> various places to allocate single/multiple blocks for inodes. I've come up
> with some data structures to accomplish recording of these allocations as
> extents.
>
> I'm proposing
Hi all,
I've been looking at rgrp.c:gfs2_alloc_blocks(), which is called from
various places to allocate single/multiple blocks for inodes. I've come up
with some data structures to accomplish recording of these allocations as
extents.
I'm proposing we add a new metadata type for journal blocks
Hi,
On 11/12/2020 16:38, Abhijith Das wrote:
Hi all,
With a recent set of patches, we nearly eliminated the per_node statfs
change files by recording that info in the journal. The files and some
recovery code remain only for backward compatibility. Similarly, I'd
like to get rid of the
Hi all,
With a recent set of patches, we nearly eliminated the per_node statfs
change files by recording that info in the journal. The files and some
recovery code remain only for backward compatibility. Similarly, I'd
like to get rid of the per_node quota change files and record that
info in the
13 matches
Mail list logo
