Hi all,
I have been reading through the XFS documentation and looking more into the on-disk structures. Previously, I had looked into AG inode management, but not inode core structure. So I thought it would be better to look into how files, directories and links are stored on disk with inodes.
I implemented struct xfs_dinode_core, the core part of the inode, which includes stat data information about data and attribute forks. Data fork and attribute fork comes after core. The following struct is used by the class inode to get the information such as modification time, user ID, no of links from directories.
Hey folks,
After implementing the superblock structure, my next task was to get the identify_partition hook working. I implemented dummy hooks (xfs_identify_parition, xfs_scan_partition) which logs some keyword so that I can trace how it’s working and in what order hooks are being called. I didn’t focus on mount hook at this point. While building I was getting the segmentation fault and wasn’t able to proceed. Adrien suggested to use GDB and try to debug and see what wrong. From the xfs_shell commands, it was clear that the xfs_shell binary was located at [/haiku/haiku/generated.x86_64/objects/linux/x86_64/release/tools/xfs_shell]. This way was to run the xfs_shell in GDB:
Hey everyone,
I was not able to put in complete effort into GSoC, as I was having exams in my University during the past few weeks. I’ll be regular with the updates starting with this one.
I was encountering issues related to header files and xfs_shell wasn’t bulding properly. It was the problem in JamFile that FS_SHELL wasn’t added as an additional define. Doing so made sure that fs-shell wrappers are properly loaded.
Hey everyone, I have been working on the project for the past two weeks and would love to share my update here as well.
My first task is to create an empty file system module and test the same on fs_shell. As fs_shell provides an interface to build and test the file system in a commandline tool, it will be easier to test the file system module.
I made an XFS image file using the following commands:
Hello everyone! My name is Abhinand and I am really happy to say that I am one of the people who has been selected for GSoC 2018. And more importantly, I will be working on adding support for XFS. If you would like to ask something to me/track my progress, I have added the contact links at the bottom of this page.
I would like to begin with a short introduction about me and the work that I did so far. I am a computer science undergraduate student from Amrita Vishwa Vidyapeetham, in India. I am active member of FOSS@Amrita, an open source community in the college, through which I got to know about Haiku. I came across the project list in Haiku while I was searching for a project to do this summer. I got interested in two of the listed projects and starting writing proposal for the same. I started reading documents related to XFS, B+Tree, and Haiku file system modules and wrote a proposal with my understanding of the project. Afterwards, I was trying to explore the BFS codebase, as it uses B+Tree to store data. I came to know that BFS uses B+Tree to store data and this implementation can be used for XFS as well. Also, I was trying to understand how the file system uses Haiku file system modules and was able to get an idea of the classes needed for the file system.
