Google Summer of Code 2007

On this page I will keep everyone updated on what I'll be doing, why I'm doing it, and when I'm doing it.

I've created a branch structure something like: //depot/projects/soc2007/lulf/<gvinumbranch>

This way i have a gvinum_main branch where everything will be imported, and a lot of other small branches where I will work on specific issues. Then I will later integrate them into the gvinum_main branch.

A code sample from my work this summer can be found here: http://folk.ntnu.no/lulf/gvinum_soc2007.tar.gz

2007-05-09

Here's a summary of what I've done so far, and might do soon.

I've committed some work on the setstate functionality making it possible to be used again. Setstate now works on subdisks, plexes, volumes and drives. I have also been thinking of and made error codes to be used internally in gvinum to sort of help me see what happens when debugging etc.

Other than that, I've rewritten the resetconfig a bit to prevent (what i think is) a race condition that was introduced with the new event system. (Testing in progress right now, so I'll commit it as soon as my test-build-tree is up-to-date.)

What I is thinking to do next is to begin fix the remaining issues with the new event system.

Also, these are my initial plans to complete in the near future:

2007-05-26

More information. It feels a bit duplicate work, but this is perhaps a place to explain more in detail of my work.

Sort of a summary of what I've done this week, and a bit on my work-in-progress.

Now, I was going to test this rebuild of degraded plexes a bit, but I'd like to have the attach/detach routines to do this instead of zeroing parts of the drive to see if it behaves correctly (avoiding erasing gvinum magic etc. But I'll probably try that first). I have the code for this from old gvinum, so I'm currently on my way to implement it for the new gvinum as well.

So, off to more coding :)

2007-06-14

So, finally the exams are over, and I've been able to work sort of full-time on my project the last days. What I've done is:

Next on my schedule is to hunt some weird state bugs where the state is not correctly set, as well as the mirrored plex problems I've seen. Also, I need to guarantee that a plex sync is up-to-date (that no data is written to the synced plex in the meantime).

2007-06-28

Finally, an update on what I've been doing since the last time. This time I have a lot of small changes that have been done:

Next, I'm going to implement concat/stripe/mirror functionality. I already have some code from previous work I did, so I just need to adapt it to new gvinum, as well as change some ugly parts. There are some small facade-changes left, but I will do this after the last of the original vinum features is completed. Also, I will try write a nice status report, and get a testable patch out by the time the report is finished.

2007-07-04

Since last post, there has been many small bugfixes to gvinum. After some debating with myself on how I should implement concat/stripe/mirror, I think I got it pretty much right. The event system changed gvinum a lot, so I had to rewrite most of the code I already had on this.

I have done a lot of testing this week, and I made a test plan that I’m going to follow. Hopefully, I’ll also be able to create som automatic tests for this.

I’ve even been a good boy and updated the gvinum manpage! I added some examples to the manpage as well, so that it’s easier to get into gvinum for inexperienced users (not sure if we want gvinum to live even longer, but :) ).

Since last post I haven’t really done that much do gvinum, but a few things.

Now, the first and second points are quite boring to do, but I had to do it. Now the last points were trickier, since I didn’t really know where I should start. Finally I decided the best way was to let the plex overwrite itself! A more detalied explanation can be found in the TODO of my perforce branch. I need to test the implementation a bit now. Other than that, I’ve been a bit lazy on my own work this week, and tried to help other students with reviews etc.

A lot of small problems with weird states being set was also fixed, since this can be very confusing if you havent used gvinum much.

What I’d like to do next, is create a set of testscripts that I can use to test quickly and easily with. I also noticed that it would be nice to have a similar command like ‘mirror’ for RAID-5 volumes. This could be used like this: ‘gvinum raid5 ‘. Other than that, I’ve started to think on how I’m going to implement raid-5 resizing and other goals in my proposal

2007-07-17

Since last post I haven’t really done that much do gvinum, but a few things.

Now, the first and second points are quite boring to do, but I had to do it. Now the last points were trickier, since I didn’t really know where I should start. Finally I decided the best way was to let the plex overwrite itself! A more detalied explanation can be found in the TODO of my perforce branch. I need to test the implementation a bit now. Other than that, I’ve been a bit lazy on my own work this week, and tried to help other students with reviews etc.

2007-08-06

The last couple of weeks I’ve tested and done bugfixing and cleanup of gvinum code. I refactored some parts to make the code belong where it seems logical. I modified some of the plex-code to make it look more like the way RAID-5 offset-calculation and request-handling is done.

I also implemented growing for striped plexes, but that was quite easy since I could reuse most of the code for growing RAID-5 plexes. Unfortunately I was sick for a week and unable to work.

What remains now is to do more testing (can’t get enough), and write and update documenatation on gvinum. I have updated patches for gvinum at http://folk.ntnu.no/lulf/patches/freebsd/gvinum for both RELENG_6 and CURRENT.

Also, I created a new perforce-branch called gvinum_cache. I’ve currently implemented a read/write-cache to check if this would give much speed-up for gvinum. It’s not very nice for reliability, but could be an option for those who want better performance.

2007-08-17

More status updates... I've been fixing many small gvinum bugs the last couple of weeks:

Probably a couple of other fixes as well. Also, I've updated the vinum-examples page in the handbook to reflect new features and more practical examples. I've posted a "call for testers" on current@, arch@ and geom@, and have received some response from people who are willing to help me test. Thanks to them.

2009-03-28

The gvinum SoC project was committed today.

UlfLilleengen/SOC (last edited 2009-03-28 17:40:47 by UlfLilleengen)