Hi Andrew,
> On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita
> wrote:
>
> > When changing the size of a block device, its all caches are freed.
> > It's necessary on shrinking to prevent spurious I/Os to the disappeared
> > region.
> > However, on expanding, such
Hi Andrew,
> On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita
> wrote:
>
> > When changing the size of a block device, its all caches are freed.
> > It's necessary on shrinking to prevent spurious I/Os to the disappeared
> > region.
> > However, on expanding, such kind of I/Os doesn't happen.
On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita
wrote:
> When changing the size of a block device, its all caches are freed.
> It's necessary on shrinking to prevent spurious I/Os to the disappeared
> region.
> However, on expanding, such kind of I/Os doesn't
On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita
wrote:
> When changing the size of a block device, its all caches are freed.
> It's necessary on shrinking to prevent spurious I/Os to the disappeared
> region.
> However, on expanding, such kind of I/Os doesn't happen.
>
> Similar things can
When changing the size of a block device, its all caches are freed.
It's necessary on shrinking to prevent spurious I/Os to the disappeared region.
However, on expanding, such kind of I/Os doesn't happen.
Similar things can be considered for btrfs filesystem resize and resize2fs,
but they are
When changing the size of a block device, its all caches are freed.
It's necessary on shrinking to prevent spurious I/Os to the disappeared region.
However, on expanding, such kind of I/Os doesn't happen.
Similar things can be considered for btrfs filesystem resize and resize2fs,
but they are
6 matches
Mail list logo