To do list

[Shentino]

My suggestion:

Forbidden zones.

Intended for both helpful defragging as well as data recovery.

Mark a section (or few) of the disk as forbidden for allocation, so
that if the fs tries to take more blocks, it doesn't use the forbidden
sections.

This can be helpful in two areas

1.  Defragmentation, to keep data and metadata from popping up in a
spot where you're trying to shove a reassembled file

2.  Recovery, to keep unchecked data from being lost by overwrite by
an allocation.

This is more of a building block than a final feature.

On Sat, Jan 12, 2013 at 5:50 AM, Shentino <shentino at gmail.com> wrote:
> Auto defrag
>
> On Fri, Jan 11, 2013 at 1:26 AM, Shentino <shentino at gmail.com> wrote:
>> I'd also like to suggest merging into the mainline as soon as possible.
>>
>> I for one am eager to test this out.
>>
>> On Thu, Jan 10, 2013 at 4:39 PM, OGAWA Hirofumi
>> <hirofumi at mail.parknet.co.jp> wrote:
>>> Daniel Phillips <daniel.raymond.phillips at gmail.com> writes:
>>>
>>>> We already talked about a possible per file "no redirect" bit. We
>>>> would need some reasonable way to set it. Autoset if bmap happens?
>>>
>>> bmap can't know whether caller is swap or ioctl. So, we would have to
>>> use ->swap_activate/swap_deactivate() instead.
>>> --
>>> OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>
>>>
>>> _______________________________________________
>>> Tux3 mailing list
>>> Tux3 at phunq.net
>>> http://phunq.net/mailman/listinfo/tux3