|
Home > Archive > Data Storage > June 2007 > Overhead of metadata block
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Overhead of metadata block
|
|
| byaarov@yahoo.com 2007-06-23, 7:14 pm |
| 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
| |
|
| byaarov@yahoo.com 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.
| |
| Faeandar 2007-06-24, 1:15 am |
| On Sat, 23 Jun 2007 15:13:33 -0700, byaarov@yahoo.com 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
| |
| byaarov@yahoo.com 2007-06-24, 7:14 am |
| On Jun 23, 8:12 pm, Faeandar <mr_casta...@yahoo.com> wrote:
> On Sat, 23 Jun 2007 15:13:33 -0700, byaa...@yahoo.com wrote:
>
>
> 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.
| |
| robertwessel2@yahoo.com 2007-06-25, 1:14 pm |
| On Jun 24, 2:55 am, byaa...@yahoo.com wrote:
> On Jun 23, 8:12 pm, Faeandar <mr_casta...@yahoo.com> wrote:
>
>
>
>
>
> 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...
| |
| byaarov@yahoo.com 2007-06-26, 1:15 am |
| On Jun 25, 10:36 am, "robertwess...@yahoo.com"
<robertwess...@yahoo.com> wrote:
> On Jun 24, 2:55 am, byaa...@yahoo.com wrote:
>
>
>
>
>
>
>
>
>
> 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.
| |
|
| byaarov@yahoo.com proclaimed:
> On Jun 23, 8:12 pm, Faeandar <mr_casta...@yahoo.com> wrote:
>
>
>
> 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
|
|
|
|
|