Overhead of metadata block

If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

proclaimed:
If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?


Depends on the file system architecture.

On Sat, 23 Jun 2007 15:13:33 -0700, wrote:

If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

Define overhead? I would think by definition it takes 4k of space.
Overhead can include space, round trip to disk (latency), memory
allocation, etc...

~F

On Jun 23, 8:12 pm, Faeandar wrote:
On Sat, 23 Jun 2007 15:13:33 -0700, wrote:
If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

Define overhead? I would think by definition it takes 4k of space.
Overhead can include space, round trip to disk (latency), memory
allocation, etc...

~F

By overhead, I meant space. I think you answered my question... an
inode (or metadata block) usually takes about the block size amount of
space.

On Jun 24, 2:55 am, wrote:
On Jun 23, 8:12 pm, Faeandar wrote:

On Sat, 23 Jun 2007 15:13:33 -0700, wrote:
If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

Define overhead? I would think by definition it takes 4k of space.
Overhead can include space, round trip to disk (latency), memory
allocation, etc...

~F

By overhead, I meant space. I think you answered my question... an
inode (or metadata block) usually takes about the block size amount of
space.


Errr... Assuming we're talking about something more or less along the
lines of a traditional *nix FS, a single inode is not anywhere near
the size of a disk block, 128 bytes being a common historical value.
If you mean an inode block, IOW, a block in the area of the disk
reserved for inodes, then it's a block...

On Jun 25, 10:36 am, "
wrote:
On Jun 24, 2:55 am, wrote:



On Jun 23, 8:12 pm, Faeandar wrote:

On Sat, 23 Jun 2007 15:13:33 -0700, wrote:
If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

Define overhead? I would think by definition it takes 4k of space.
Overhead can include space, round trip to disk (latency), memory
allocation, etc...

~F

By overhead, I meant space. I think you answered my question... an
inode (or metadata block) usually takes about the block size amount of
space.

Errr... Assuming we're talking about something more or less along the
lines of a traditional *nix FS, a single inode is not anywhere near
the size of a disk block, 128 bytes being a common historical value.
If you mean an inode block, IOW, a block in the area of the disk
reserved for inodes, then it's a block...

Yes, I meant actual physical space taken on disk by the data being
represented by the inode information.

proclaimed:

On Jun 23, 8:12 pm, Faeandar wrote:

On Sat, 23 Jun 2007 15:13:33 -0700, wrote:

If I have a 4K block size file system, what is the overhead of the
space taken by the metadata block for a file?

B

Define overhead? I would think by definition it takes 4k of space.
Overhead can include space, round trip to disk (latency), memory
allocation, etc...

~F


By overhead, I meant space. I think you answered my question... an
inode (or metadata block) usually takes about the block size amount of
space.

and then some file systems store acls in another block for ease of
manipulation