* Physical block addresses?
@ 2008-01-28 17:48 Sivan Toledo
[not found] ` <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Sivan Toledo @ 2008-01-28 17:48 UTC (permalink / raw)
To: users-JrjvKiOkagjYtjvyW6yDsg
Hi,
I am trying to figure out whether NILFS uses physical block addresses
as pointers in inodes and indirect blocks, but I could not figure this
out from the papers.
Does it? If so, I assume that when cleaning a segment and copying live
data to a new segment, each relocated block causes the propagation of
dirty blocks (because some other blocks point to the old segment, so
they need to be modified, and so on. Is that correct?
Thanks, Sivan Toledo
^ permalink raw reply [flat|nested] 2+ messages in thread[parent not found: <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Physical block addresses? [not found] ` <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2008-01-31 6:25 ` Koji Sato 0 siblings, 0 replies; 2+ messages in thread From: Koji Sato @ 2008-01-31 6:25 UTC (permalink / raw) To: NILFS Users mailing list Hi, Sivan. > I am trying to figure out whether NILFS uses physical block addresses > as pointers in inodes and indirect blocks, but I could not figure this > out from the papers. > > Does it? If so, I assume that when cleaning a segment and copying live > data to a new segment, each relocated block causes the propagation of > dirty blocks (because some other blocks point to the old segment, so > they need to be modified, and so on. Is that correct? NILFS version 2 uses virtual block numbers to point to blocks. The virtual block numbers are translated into physical disk addresses when they are referenced. This mechanism prevents cascading updates of the file system when cleaning segments because only the virtual-to-physical mappings are updated. Thanks. -- Koji Sato Open Source Software Computing Project NTT Cyber Space Laboratories Nippon Telegraph and Telephone Corporation ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-01-31 6:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-28 17:48 Physical block addresses? Sivan Toledo
[not found] ` <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-31 6:25 ` Koji Sato
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.