Meeting

Sun Nov 30 13:59:47 CST 2014

Hi,

We've now resumed working on the xfs_fsr utility as discussed before, after
our exams.

The first task that we undertook was to use fiemap to get file extent
mappings and tried to correlate the output with the information obtained
from xfs_bmap. For this we used the two underlying structures fiemap
and fiemap_extent. We're now trying to use the available free space mapping
patches to get free spaces in the file system.

We also wanted to ask about the current status of the rmap, as we'll
be required to define the interfaces that query it, as a key component of
our
work.

Regards,
A-DRS.

On Mon, Dec 1, 2014 at 1:01 AM, Swapnil Pimpale <pimpale.swapnil at gmail.com>
wrote:

> Just say that you have resumed work on the project after the exam.
>
> On Sun, Nov 30, 2014 at 2:16 PM, Somdeep Dey <somdeepdey10 at gmail.com>
> wrote:
>
>> This is the final draft :
>> Hi,
>> We were occupied with our exams for the last two months.
>> We've now resumed working on the xfs_fsr utility as discussed before.
>>
>> The first task that we undertook was to use fiemap to get file extent
>> mappings and tried to correlate the output with the information obtained
>> from xfs_bmap. For this we used the two underlying structures fiemap
>> and fiemap_extent. We're now trying to use the available free space
>> mapping
>> patches to get free spaces in the file system.
>>
>> We also wanted to ask about the current status of the rmap, as we'll
>> be required to define the interfaces that query it, as a key component of
>> our
>> work.
>>
>> Regards,
>> A-DRS.
>>
>> On Sun, Nov 30, 2014 at 11:55 PM, Somdeep Dey <somdeepdey10 at gmail.com>
>> wrote:
>>
>>> Hi,
>>> We were occupied with our exams for the last two months.
>>> We've now resumed working on the xfs_fsr utility as discussed before.
>>>
>>> The first task that we undertook was to use fiemap to get file extent
>>> mappings and tried to correlate the output with the information obtained
>>> from xfs_bmap. For this we used the two underlying structures fiemap
>>> and fiemap_extent. We're now trying to use the available free space
>>> mapping
>>> patches to get free spaces in the file system.
>>>
>>> We also wanted to ask about the current status of the rmap, as we'll
>>> be required to define the interfaces that query it, as a key component
>>> of our
>>> work.
>>>
>>> Regards,
>>> A-DRS.
>>>
>>> On Sun, Nov 30, 2014 at 9:37 PM, Nafisa Mandliwala <
>>> nafisa.mandliwala at gmail.com> wrote:
>>>
>>>> Umm, no need to apologize.
>>>>
>>>> What you showed me on Thursday was the standard fiemap ioctl that gives
>>>> the extents used by a file.
>>>> Say that you're now trying to use Dave's freespace mapping patches to
>>>> get free spaces in the file system.
>>>> Also, you're going to *define* the interfaces needed to query the
>>>> rmap, not just query them.
>>>>
>>>> Looks fine otherwise.
>>>>
>>>> On Sun, Nov 30, 2014 at 9:16 PM, Somdeep Dey <somdeepdey10 at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> This is the mail we drafted for Dave :
>>>>>
>>>>> Hi,
>>>>> We'd like to apologise for our unavailability over the last two months
>>>>> given the occurrence of our exams. We've now resumed working on the
>>>>> xfs_fsr utility as discussed before.
>>>>>
>>>>> The first task that we undertook was to use fiemap to get file extent
>>>>> mappings and tried to correlate the output with the information
>>>>> obtained
>>>>> from xfs_bmap. For this we used the two underlying structures fiemap
>>>>> and fiemap_extent.
>>>>>
>>>>> We also wanted to ask about the current status of the rmap, as we'll
>>>>> be required to query the interfaces of that as a key component of our
>>>>> work.
>>>>>
>>>>> Regards,
>>>>> A-DRS.
>>>>>
>>>>>
>>>>> Do tell us if this will suffice.
>>>>> Thanks,
>>>>> A-DRS.
>>>>>
>>>>> On Sun, Nov 30, 2014 at 9:05 PM, Somdeep Dey <somdeepdey10 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>> This is the mail we drafted for Dave :
>>>>>>
>>>>>> Hi,
>>>>>> We'd like to apologise for our unavailability over the last two months
>>>>>> given the occurrence of our exams. We've now resumed working on the
>>>>>> xfs_fsr utility as discussed before.
>>>>>>
>>>>>> The first task that we undertook was to use fiemap to get file extent
>>>>>> mappings and tried to correlate the output with the information
>>>>>> obtained
>>>>>> from xfs_bmap. For this we used the two underlying structures fiemap
>>>>>> and fiemap_extent.
>>>>>>
>>>>>> We also wanted to ask about the current status of the rmap, as we'll
>>>>>> be required to query the interfaces of that as a key component of our
>>>>>> work.
>>>>>>
>>>>>> Regards,
>>>>>> A-DRS.
>>>>>>
>>>>>>
>>>>>> Do tell us if this will suffice.
>>>>>> Thanks,
>>>>>> A-DRS.
>>>>>>
>>>>>> On Thu, Nov 27, 2014 at 9:39 PM, Nafisa Mandliwala <
>>>>>> nafisa.mandliwala at gmail.com> wrote:
>>>>>>
>>>>>>> Guys, you can find the xfs_alloc.h, xfs_alloc.c and xfs_iops.c in
>>>>>>> linux-x.x.x/fs/xfs/
>>>>>>> Please check if it has the changes we're looking for.
>>>>>>>
>>>>>>> I couldn't find anything on rmap, you should write a mail asap.
>>>>>>>
>>>>>>> On Thu, Nov 27, 2014 at 2:40 AM, Somdeep Dey <somdeepdey10 at gmail.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>> We ran the code for fiemap on files, that included  the following
>>>>>>>> three types :
>>>>>>>> 1) A non-fragmented file
>>>>>>>> 2) A fragmented file before using xfs_fsr
>>>>>>>> 3) The defragmeneted equivalent of the above file after using
>>>>>>>> xfs_fsr
>>>>>>>>
>>>>>>>>
>>>>>>>> Thereafter we examined the data by printing the fiemap structure
>>>>>>>> and fiemap_extents struct. The logs for the process followed is also
>>>>>>>> attached here.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> A-DRS.
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "ADRScube" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to adrscube+unsubscribe at googlegroups.com.
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/msgid/adrscube/CAJAKVEFdkSEMW84%3DTvRNqOQdNMz6nS_WRVGN-2MX5se9NUaV1A%40mail.gmail.com
>>>>>>>> <https://groups.google.com/d/msgid/adrscube/CAJAKVEFdkSEMW84%3DTvRNqOQdNMz6nS_WRVGN-2MX5se9NUaV1A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>>
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "ADRScube" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to adrscube+unsubscribe at googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/adrscube/CAJAKVEE2Lu%3DMReV9fdg0L4OvWAymJJv9qteNDm_1oHyNNcdKVw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/adrscube/CAJAKVEE2Lu%3DMReV9fdg0L4OvWAymJJv9qteNDm_1oHyNNcdKVw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>         Swapnil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20141201/18c77a4e/attachment.html>