kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: chengwei.yang@intel.com (Yang Chengwei)
To: kernelnewbies@lists.kernelnewbies.org
Subject: first block in ext3 filesystem
Date: Wed, 8 Aug 2012 18:28:38 +0800	[thread overview]
Message-ID: <20120808102838.GC19096@chengwei-debian> (raw)
In-Reply-To: <CAE0An6fJFFgh_UMVkczD+iBaiLJpMg1DQomgzGmKkPrvLjrP9g@mail.gmail.com>

On Mon, Aug 06, 2012 at 11:19:57AM -0700, Manish Katiyar wrote:
> 
> On Mon, Aug 6, 2012 at 11:04 AM, Prashant Shah <pshah.mumbai@gmail.com> wrote:
> 
>     Hi,
> 
>     I came across this
> 
>     $sudo dumpe2fs /dev/sda1
> 
>     4KB Block Size
>     Group 0: (Blocks 0-32767)
>       Primary superblock at 0, Group descriptors at 1-1
> 
>     1KB Block Size
>     Group 0: (Blocks 1-8192)
>       Primary superblock at 1, Group descriptors at 2-2
> 
>     Why does first block start from 0 in the 4KB block size partition and
>     1 in 1KB block size partition ?
> 
> 
> Let's say superblock is always written at a fixed offset of 1024 (they have to
As Shah said, the superblock is always written at a offset 1024. When
the block size is 4096, offset 1024 is in the first block (block 0),
while the block size is 1024, offset 1024 is in the second block (block
1).

Since group descriptor locates after superblock, so Group 0 starts from
1 when the block size is 1024 byte.

Please correct me if I'm wrong.

--
Thanks,
Chengwei

> because e2fsck has to find it) in the filesystem. What would be the block
> numbers with block sizes 1k and 4k ?
> 
>  
> 
> 
>     Regards.
> 
>     _______________________________________________
>     Kernelnewbies mailing list
>     Kernelnewbies at kernelnewbies.org
>     http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
> 
> 
> 
> --
> Thanks -
> Manish
> 

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120808/c3c39766/attachment.bin 

  parent reply	other threads:[~2012-08-08 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 18:04 first block in ext3 filesystem Prashant Shah
2012-08-06 18:19 ` Manish Katiyar
2012-08-06 18:27   ` Prashant Shah
2012-08-08 10:28   ` Yang Chengwei [this message]
2012-08-07  6:03 ` Mulyadi Santosa

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=20120808102838.GC19096@chengwei-debian \
    --to=chengwei.yang@intel.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).