nilfs2: keep zero value in i_cno except for gc-inodes
On-memory inode structures of nilfs have a member "i_cno" which stores a checkpoint number related to the inode. For gc-inodes, this field indicates version of data each gc-inode caches for GC. Log writer temporarily uses "i_cno" to transfer the latest checkpoint number. This stops the latter use and lets only gc-inodes use it. The purpose of this patch is to allow the successive change use "i_cno" for inode lookup. Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
This commit is contained in:
parent
7d6cd92fe2
commit
6c43f41000
3 changed files with 24 additions and 16 deletions
|
@ -270,6 +270,14 @@ struct nilfs_super_block {
|
|||
#define NILFS_MIN_NRSVSEGS 8 /* Minimum number of reserved
|
||||
segments */
|
||||
|
||||
/*
|
||||
* We call DAT, cpfile, and sufile root metadata files. Inodes of
|
||||
* these files are written in super root block instead of ifile, and
|
||||
* garbage collector doesn't keep any past versions of these files.
|
||||
*/
|
||||
#define NILFS_ROOT_METADATA_FILE(ino) \
|
||||
((ino) >= NILFS_DAT_INO && (ino) <= NILFS_SUFILE_INO)
|
||||
|
||||
/*
|
||||
* bytes offset of secondary super block
|
||||
*/
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue