From: Vitaly Fertman <vitaly@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] storing SOM epoch in EA
Date: Tue, 19 Feb 2008 13:59:47 +0300 [thread overview]
Message-ID: <200802191359.47379.vitaly@sun.com> (raw)
In-Reply-To: <47BAAF3F.6030301@sun.com>
> hi!
>
> Can we use IAM for storing epoch? It is fast and does not have such
> strong size limitations.
there are no size limitations, EA can be stored in a separate
block, we just want to minimize IO.
> We could make "epoch" index in mkfs time (like
> it is done for existing indexes now) and use object's fid as a key and
> epoch as value.
this looks like it will double IO/seeks for each inode.
--
Vitaly
next prev parent reply other threads:[~2008-02-19 10:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 9:48 [Lustre-devel] storing SOM epoch in EA Alex Zhuravlev
2008-02-19 10:28 ` Yuriy Umanets
2008-02-19 10:30 ` Alex Zhuravlev
2008-02-19 10:38 ` Yuriy Umanets
2008-02-19 10:59 ` Vitaly Fertman [this message]
2008-02-19 11:11 ` Yuriy Umanets
2008-02-19 11:18 ` Alex Zhuravlev
2008-02-19 12:02 ` Yuriy Umanets
2008-02-19 12:09 ` Alex Zhuravlev
2008-02-19 14:28 ` Yuriy Umanets
2008-02-19 14:47 ` Alex Zhuravlev
2008-02-19 15:10 ` Yuriy Umanets
2008-02-19 12:13 ` Alex Zhuravlev
2008-02-19 14:30 ` Yuriy Umanets
2008-02-19 14:36 ` Nikita Danilov
2008-02-19 14:44 ` Yuriy Umanets
2008-02-19 14:39 ` Yuriy Umanets
2008-02-19 14:42 ` Alex Zhuravlev
2008-02-19 20:13 ` Andreas Dilger
2008-02-19 14:59 ` Mikhail Pershin
2008-02-19 15:11 ` Kalpak Shah
2008-02-19 15:23 ` Ricardo M. Correia
2008-02-19 15:14 ` Yuriy Umanets
2008-02-19 15:19 ` Alex Zhuravlev
2008-02-19 15:28 ` Vitaly Fertman
2008-02-19 15:18 ` Ricardo M. Correia
2008-02-19 16:21 ` Nikita Danilov
2008-02-19 16:27 ` Alex Zhuravlev
2008-02-20 16:10 ` Nikita Danilov
2008-02-19 15:31 ` Eric Barton
2008-02-19 15:42 ` Alex Zhuravlev
2008-02-19 20:19 ` Andreas Dilger
2008-02-19 20:33 ` [Lustre-devel] on-disk SOM attributes [former storing SOM epoch in EA] Vitaly Fertman
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=200802191359.47379.vitaly@sun.com \
--to=vitaly@sun.com \
--cc=lustre-devel@lists.lustre.org \
/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.