Hello everybody! It’s been a while since my previous post.
This post is a short summary of all work done upto this point.
During the past few weeks, I was able to add the following features to the
current btrfs implementation
Creating new files
The basic algorithm behind creating new files is allocating a new inode,
updating the fs tree to reflect this, creating a hard link in the directory
containing the file and finally updating the cache. However, we must make sure
to deallocate memory and clean up any partial changes in case of any errors.
Hello everybody! It’s been a while since my previous post.
This post is a short summary of all the work done upto this point. For a
detailed report of every day, visit this blog I set up using Blogger.
Week 1
As mentioned in my proposal, the target for week #1
was document the current btrfs implementation. As part of this, I documented
the following classes
- Chunk
- Inode
- BTree
- Attribute
- AttributeIterator
- DirectoryIterator
Week #1 went smoothly without any problems.
Introduction
Hello, world!
As some of you might be aware, I’m one of the students selected for
GSoC 2019. My name is Bharathi Ramana Joshi. You may know me as brj, my
initials, from the mailing lists and IRC channel. I’m pursuing an underguate
degree in Computer Science and Engineering from Keshav Memorial Institute of
Technology, India.
Project: Improving the btrfs filesystem
As the title suggests, I shall be working on Haiku’s btrfs implementation for
most of the summer. Currently, it is possible to read and write directories but
only read from files. By the end of GSoC 2019, I aim to implement file writing.
