All of lore.kernel.org
 help / color / mirror / Atom feed
* File system implementation
@ 2013-05-25  5:17 Dibyayan Chakraborty
  2013-05-26 11:39 ` Greg Freemyer
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Dibyayan Chakraborty @ 2013-05-25  5:17 UTC (permalink / raw)
  To: kernelnewbies

Hi,
I want to implement a file system and integrate with my system. Now
first i have to implement the code for disk-formatting(like populating
the super_block , root inode etc). I want to see the source code for the
ext3 file system for this purpose.

Please tell me which file in the kernel source contains the
implementation.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* File system implementation
  2013-05-25  5:17 File system implementation Dibyayan Chakraborty
@ 2013-05-26 11:39 ` Greg Freemyer
  2013-05-26 18:23 ` Sankar P
  2013-05-27  8:05 ` Vineet Agarwal
  2 siblings, 0 replies; 6+ messages in thread
From: Greg Freemyer @ 2013-05-26 11:39 UTC (permalink / raw)
  To: kernelnewbies



Dibyayan Chakraborty <dib.coolguy@gmail.com> wrote:

>Hi,
>I want to implement a file system and integrate with my system. Now
>first i have to implement the code for disk-formatting(like populating
>the super_block , root inode etc). I want to see the source code for
>the
>ext3 file system for this purpose.
>
>Please tell me which file in the kernel source contains the
>implementation.

In general the kernel doesn't create the things. Mkfs does, so you need the source to mkfs.ext3.

Greg
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* File system implementation
  2013-05-25  5:17 File system implementation Dibyayan Chakraborty
  2013-05-26 11:39 ` Greg Freemyer
@ 2013-05-26 18:23 ` Sankar P
  2013-05-27  8:05 ` Vineet Agarwal
  2 siblings, 0 replies; 6+ messages in thread
From: Sankar P @ 2013-05-26 18:23 UTC (permalink / raw)
  To: kernelnewbies

On Sat, May 25, 2013 at 10:47 AM, Dibyayan Chakraborty
<dib.coolguy@gmail.com> wrote:
> Hi,
> I want to implement a file system and integrate with my system. Now
> first i have to implement the code for disk-formatting(like populating
> the super_block , root inode etc). I want to see the source code for the
> ext3 file system for this purpose.
>
> Please tell me which file in the kernel source contains the
> implementation.
>

I did the same thing few days back and asked the same question few days back :)

It is very simple. All you need is to codify your structs. Then write
a simple mkfs-yourfs.c which will fopen the given input file, write
(by type casting to a char *) the struct pointer which contains your
filesystem structure and then closes the file. It is as simple as that
:)

All the best.

--
Sankar P
http://psankar.blogspot.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* File system implementation
  2013-05-25  5:17 File system implementation Dibyayan Chakraborty
  2013-05-26 11:39 ` Greg Freemyer
  2013-05-26 18:23 ` Sankar P
@ 2013-05-27  8:05 ` Vineet Agarwal
  2 siblings, 0 replies; 6+ messages in thread
From: Vineet Agarwal @ 2013-05-27  8:05 UTC (permalink / raw)
  To: kernelnewbies

On Sat, May 25, 2013 at 10:47 AM, Dibyayan Chakraborty <
dib.coolguy@gmail.com> wrote:

> Hi,
> I want to implement a file system and integrate with my system. Now
> first i have to implement the code for disk-formatting(like populating
> the super_block , root inode etc). I want to see the source code for the
> ext3 file system for this purpose.
>
> Please tell me which file in the kernel source contains the
> implementation.
>
>
>
You can start looking for e2fsprogs. You can find the details out there
regarding the file-system formatting etc.


>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130527/d18527bf/attachment.html 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* File System Implementation
  2013-05-29 14:20 File System Implementation Dibyayan Chakraborty
@ 2013-05-29 15:54 ` Greg Freemyer
  0 siblings, 0 replies; 6+ messages in thread
From: Greg Freemyer @ 2013-05-29 15:54 UTC (permalink / raw)
  To: kernelnewbies

Historically filesystem designers knew what legal values of the
various parameters were and they simply looked for legal values.  If
they found any illegal values, they reset them to a legal value.

In many cases, that missed bit-rot situations they wanted to find, so
with many modern filesystems, they add a CRC field to the main
datastructures, then do a CRC verification as appropriate.

XFS is right now in the middle of getting a whole bunch of CRC
functionality added.  I don't know if it is on the generation side, or
just on the verification side.
A quick google found this overview email to a patch series.  The
series may have been posted again since then.

http://comments.gmane.org/gmane.comp.file-systems.xfs.general/51575

Notice there are links to the 3 previous overview emails.  Go back and
read those, they may provide more background.

Greg

On Wed, May 29, 2013 at 10:20 AM, Dibyayan Chakraborty
<dib.coolguy@gmail.com> wrote:
> Hi,
> I was implementing a file system and ran into the following problem.
>
> I wanted to replicate the super block data in order to recover from
> occasional Hard disk failures (bit rot problem etc.). While replicating was
> easy i could not find a way to detect the errors in the first place.
>
> Any ideas and explanation will be help full.
>
> --
> With Regards
> Dibyayan Chakraborty
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* File System Implementation
@ 2013-05-29 14:20 Dibyayan Chakraborty
  2013-05-29 15:54 ` Greg Freemyer
  0 siblings, 1 reply; 6+ messages in thread
From: Dibyayan Chakraborty @ 2013-05-29 14:20 UTC (permalink / raw)
  To: kernelnewbies

Hi,
I was implementing a file system and ran into the following problem.

I wanted to replicate the super block data in order to recover from
occasional Hard disk failures (bit rot problem etc.). While replicating was
easy i could not find a way to detect the errors in the first place.

Any ideas and explanation will be help full.

-- 
With Regards
Dibyayan Chakraborty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130529/593fa540/attachment-0001.html 

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-05-29 15:54 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-25  5:17 File system implementation Dibyayan Chakraborty
2013-05-26 11:39 ` Greg Freemyer
2013-05-26 18:23 ` Sankar P
2013-05-27  8:05 ` Vineet Agarwal
2013-05-29 14:20 File System Implementation Dibyayan Chakraborty
2013-05-29 15:54 ` Greg Freemyer

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.