From: bbboson@gmail.com (Madper)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Creating mkfs for my custom filesystem
Date: Fri, 29 Mar 2013 21:23:24 +0800 [thread overview]
Message-ID: <515595CC.7040703@gmail.com> (raw)
In-Reply-To: <CAMSEaH61+srmYa+1n7q9iqOXWh36Yz5VfHQEyykycJqaEGR=dQ@mail.gmail.com>
On 03/29/2013 06:48 PM, Sankar P wrote:
> On Fri, Mar 29, 2013 at 3:56 PM, Pranay Srivastava <pranjas@gmail.com> wrote:
>> ---------- Forwarded message ----------
>> From: Pranay Srivastava <pranjas@gmail.com>
>> Date: Fri, 29 Mar 2013 15:53:21 +0530
>> Subject: Re: Creating mkfs for my custom filesystem
>> To: Sankar P <sankar.curiosity@gmail.com>
>>
>>
>>
>> On 3/29/13, Sankar P <sankar.curiosity@gmail.com> wrote:
>>> Hi,
>>>
>>> I am trying to write a simple filesystem to learn the basics of it.
>>>
>>> I have decided on a simple layout for my filesystem where the first
>>> block will be the super block and will contain the version
>>> information etc. The second block will contain the list of inodes.
>>> Third block onwards will be data blocks. Each file can grow only up to
>>> a single block size. Thrid block will represent the first file, fourth
>>> block for the second file and so on. Directories will not be
>>> supported.
>>>
>>> Now I want to create a mkfs for my filesystem as mentioned above. But
>>> I am not able to find out how to do the mkfs for my filesystem such
>>> that the generic mkfs utility will understand my filesystem. What APIs
>>> should I be using ?
>>>
>>> Any help is appreciated. Thanks.
>>>
>>> --
>>> Sankar P
>>> http://psankar.blogspot.com
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>> Hi Sankar,
>>
>> I started with something like that. Although I wrote just a bit more
>> complex but it really is quite simple. If you want you can use this
>> and I'll also like to contribute to it.
>>
>> https://github.com/pranjas/psfs.git
>>
>> Checkout psfs.h and psfs-format.c for complete details. Let me know if
>> you need any help.
>>
> Thank you.
>
> Yours seems a bit complex with support for extents etc. I am planning
> to start as simple as it could be. However, I believe your code will
> help me to find the right APIs I need. I will let you know once I
> publish my code. Your code should be very helpful to me. Thanks.
Howdy Sankar,
I found a simple mkfs's code. Hope it's helpful to you.
-- https://github.com/mkatiyar/testfs/blob/master/util/mktestfs.c
--
Best,
Madper Xie.
>
> --
> Sankar P
> http://psankar.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2013-03-29 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 8:27 Creating mkfs for my custom filesystem Sankar P
2013-03-29 9:58 ` Tobias Boege
2013-03-29 10:14 ` Sankar P
2013-03-29 13:23 ` Valdis.Kletnieks at vt.edu
2013-03-29 14:01 ` Tobias Boege
2013-03-29 15:45 ` Sankar P
[not found] ` <CA+aCy1EC-tRUCVuP-h=UV0k0bPnhcs9mu+cGFSJt_wRxCKuD-w@mail.gmail.com>
2013-03-29 10:26 ` Fwd: " Pranay Srivastava
2013-03-29 10:48 ` Sankar P
2013-03-29 13:23 ` Madper [this message]
2013-03-29 17:27 ` Manish Katiyar
2013-03-29 18:17 ` Sankar P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515595CC.7040703@gmail.com \
--to=bbboson@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).