<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Irregular Expressions &#187; super block</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/Irregular-Expressions/tag/super-block/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions</link>
	<description>Insight into current security related events and exploits, including virtualization security and tips.</description>
	<lastBuildDate>Sun, 28 Apr 2013 08:00:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>The EXT file system &#8211; Part 3</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-3/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-3/#comments</comments>
		<pubDate>Wed, 24 Aug 2011 02:12:19 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[block bitmap]]></category>
		<category><![CDATA[ext explanation]]></category>
		<category><![CDATA[group descriptor tables]]></category>
		<category><![CDATA[inode bitmap]]></category>
		<category><![CDATA[super block]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/?p=642</guid>
		<description><![CDATA[We also have to deal with the block pointers in the inodes.  Each inode can store the address of 12 blocks to store the data.  So what happens when you need more then 12 blocks to store the data? You use indirect block pointers, instead of pointing at blocks of data.  You point at blocks [...]]]></description>
				<content:encoded><![CDATA[<p>We also have to deal with the block pointers in the inodes.  Each inode can store the address of 12 blocks to store the data.  So what happens when you need more then 12 blocks to store the data?</p>
<p>You use indirect block pointers, instead of pointing at blocks of data.  You point at blocks that point to the blocks.  Basically lists of lists.</p>
<p>The first layer of this is called single indirect block pointers, the lists of lists.  Then we go to double indirect block pointers.  Lists of lists of lists.  Then down to triple indirect block pointers, lists of lists of lists of lists.</p>
<p><img src="http://upload.wikimedia.org/wikipedia/commons/a/a2/Ext2-inode.gif" alt="Wikipedia block pointers" /></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The EXT file system &#8211; Part 2</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-2/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-2/#comments</comments>
		<pubDate>Sat, 20 Aug 2011 03:01:48 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[block bitmap]]></category>
		<category><![CDATA[ext explanation]]></category>
		<category><![CDATA[group descriptor tables]]></category>
		<category><![CDATA[inode bitmap]]></category>
		<category><![CDATA[super block]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/?p=634</guid>
		<description><![CDATA[The still short version of what happens when you need locate a file on the system is the following; The SuperBlock is read, to collect information about the file system. Next to the Group Descriptor Table (After the SuperBlock on the disk), collection of information about the block groups. Once the block group that the [...]]]></description>
				<content:encoded><![CDATA[<p>The still short version of what happens when you need locate a file on the system is the following;</p>
<ul>
<li>The SuperBlock is read, to collect information about the file system.</li>
<li>Next to the Group Descriptor Table (After the SuperBlock on the disk), collection of information about the block groups.</li>
<li>Once the block group that the file resides in is determined, the group descriptor table is used to locate where the Inode Table is.</li>
<li>The Inode Table will point us to the block root directory entries.</li>
<li>That is opened to locate the folder that contains the file we are looking for.</li>
<li>Now we have the inode of the folder, we then determine the block group it belongs to (we use information from the SuperBlock for that).</li>
<li>Then we go to that block group and get the location of the folder.</li>
<li>Now we can open the block the contains the folder.</li>
</ul>
<div>And this will keep going until the location of the file is found depending on the number of sub folders, then the information will be pulled out of the blocks that contain the information.</div>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The EXT file system &#8211; Part 1</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-1/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-1/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 04:34:44 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[block bitmap]]></category>
		<category><![CDATA[ext explanation]]></category>
		<category><![CDATA[group descriptor tables]]></category>
		<category><![CDATA[inode bitmap]]></category>
		<category><![CDATA[super block]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/?p=627</guid>
		<description><![CDATA[Partitions are just fine, but how does the system get to a file on the disk? On a EXT based system, the short answer is the information is stored in the Inode Table. That really does not mean much if you don&#8217;t have understanding of what the filesystem looks like. A little explanation is needed. [...]]]></description>
				<content:encoded><![CDATA[<p>Partitions are just fine, but how does the system get to a file on the disk?</p>
<p>On a EXT based system, the short answer is the information is stored in the Inode Table.</p>
<p>That really does not mean much if you don&#8217;t have understanding of what the filesystem looks like.</p>
<p>A little explanation is needed.</p>
<p>The first section of the filesystem is going to contain the Super Block (block 1), there could be boot code in front of that (Unused).  The Super block contains information about the file system, such as block sizes, total number of inodes and the volume name to list a few.</p>
<p>Following the Super Block is the Group Descriptor Tables, this is what we need. This will have a backup of the Super Block, and contains the Block Bitmap, Inode Bitmap and group descriptor data structure for every block in group in the filesystem.  These are the basic structures we need to locate information on the disk.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/the-ext-file-system-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
