From: Damien Guibouret <damien.guibouret@partition-saving.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Remarks regarding sparse_super2 feature
Date: Wed, 11 May 2016 20:50:32 +0200 [thread overview]
Message-ID: <57337EF8.5090008@partition-saving.com> (raw)
In-Reply-To: <20160510232845.GC30312@thunk.org>
Theodore Ts'o wrote:
> On Sat, Apr 30, 2016 at 05:23:58PM +0200, Damien Guibouret wrote:
>
[...]
>
>
>>For the other case (shrinking the fs) at line 856:
>> if (last_bg > 1 &&
>> old_fs->super->s_backup_bgs[1] == old_last_bg)
>> fs->super->s_backup_bgs[1] = last_bg;
>>what ensures the location where the new super block backup will be set is a
>>free block?
>
>
> This is handled by reserve_sparse2_last_group(). We have to deal this
> sort of thing whenever we need to do things like grow the group
> descriptors, and we will relocate data blocks as necessary to make
> room for blocks that have to be at specific locations. (This means we
> have allocate new blocks for the blocks we are moving, copy the data
> blocks, and then update the inode(s) to point the new block
> locations.)
>
> Cheers,
>
> - Ted
Hello,
Thanks for the feedback.
For the last point, you're right, I did not look deep enough in the remaining
part of the code (and it looks obvious that when shrinking the fs, there is some
need to reallocate blocks).
Regards,
Damien
prev parent reply other threads:[~2016-05-11 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 15:23 Remarks regarding sparse_super2 feature Damien Guibouret
2016-05-10 23:28 ` Theodore Ts'o
2016-05-11 18:50 ` Damien Guibouret [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57337EF8.5090008@partition-saving.com \
--to=damien.guibouret@partition-saving.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.