search for: di_nlink

Il 17/07/20 10:54, Karl Vogel ha scritto: > It depends on the size of the variables in the structure used by the > stat() call. In ext4, the "links" variable is an unsigned 16-bit integer, > so you have your limit of 64k or so. I've worked with systems where > the limit was a signed 16-bit integer, so it maxed out at 32k. > > XFS may be a full 32-bit integer, so

..._______ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos Have a look at https://mirrors.edge.kernel.org/pub/linux/utils/fs/xfs/docs/xfs_filesystem_structure.pdf On page 105 the inode structure is given: __uint16_t di_onlink; ... __uint32_t di_nlink Page 107 gives more detail: di_onlink: In v1 inodes, this specifies the number of links to the inode from directories. When the number exceeds 65535,the inode is converted to v2 and the link count is stored in di_nlink. di_nlink: Specifies the number of links to the inode from directories. Thi...

...* mode and type of file */ + uint8_t di_version; /* inode version */ + uint8_t di_format; /* format of di_c data */ + uint16_t di_onlink; /* old number of links to file */ + uint32_t di_uid; /* owner's user id */ + uint32_t di_gid; /* owner's group id */ + uint32_t di_nlink; /* number of links to file */ + uint16_t di_projid_lo; /* lower part of owner's project id */ + uint16_t di_projid_hi; /* higher part owner's project id */ + uint8_t di_pad[6]; /* unused, zeroed space */ + uint16_t di_flushiter; /* incremented on flush */ + xfs_timestamp...

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed