All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] What are the purposes of GLOBAL_INODE_ALLOC_SYSTEM_INODE and BAD_BLOCK_SYSTEM_INODE system file
Date: Sun, 9 Oct 2016 18:33:50 +0800	[thread overview]
Message-ID: <57FA1D0E.3020204@huawei.com> (raw)
In-Reply-To: <57FA748D020000F90004EEB3@prv-mh.provo.novell.com>

Hi Gang,
GLOBAL_INODE_ALLOC_SYSTEM_INODE is used for system file inodes
allocation, you can refer mkfs.c for details.

Thanks,
Joseph

On 2016/10/9 16:47, Gang He wrote:
> Hello Guys,
> 
> If you use debugfs.ocfs2 to list system files for a ocfs2 file system, you can find these two system files.
> sles12sp1-node1:/ # debugfs.ocfs2 /dev/sdb1
> debugfs.ocfs2 1.8.2
> debugfs: ls //
>  6               16   1    2  .
>  6               16   2    2  ..
>  7               24   10   1  bad_blocks             << ==  BAD_BLOCK_SYSTEM_INODE
>  8               32   18   1  global_inode_alloc     << ==  GLOBAL_INODE_ALLOC_SYSTEM_INODE
>   ....
> 
> But, What are the purposes of GLOBAL_INODE_ALLOC_SYSTEM_INODE and BAD_BLOCK_SYSTEM_INODE system file?
> For BAD_BLOCK_SYSTEM_INODE system file, it looks to be used to store bad blocks for a file system partition, but from the code, there is not any code for this system file.
> For GLOBAL_INODE_ALLOC_SYSTEM_INODE system file, there is also not any code for it, what is the purpose of this file ?
> 
> 
> Thanks
> Gang
> 
> 
> 
> 
> 
> .
> 

  parent reply	other threads:[~2016-10-09 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09  8:47 [Ocfs2-devel] What are the purposes of GLOBAL_INODE_ALLOC_SYSTEM_INODE and BAD_BLOCK_SYSTEM_INODE system file Gang He
2016-10-09  9:00 ` Junxiao Bi
2016-10-09 10:33 ` Joseph Qi [this message]
2016-10-10  1:51   ` Gang He

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=57FA1D0E.3020204@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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 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.