|
Home > Archive > Data Storage > March 2006 > WAFL snapshots implementation
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 |
WAFL snapshots implementation
|
|
| Ashwani 2006-03-31, 12:15 am |
| Assume a file /home/test in the WAFL filesystem and its snapshot as
/.snapshot/hourly.x/test
Both of them are having the same inode number say INO
Now if /home/test is changed, why doesnt its inode number change, since
INO will be needed to represent /.snapshot/hourly.x/test?
| |
| Bill Todd 2006-03-31, 12:15 am |
| Ashwani wrote:
> Assume a file /home/test in the WAFL filesystem and its snapshot as
> /.snapshot/hourly.x/test
> Both of them are having the same inode number say INO
> Now if /home/test is changed, why doesnt its inode number change, since
> INO will be needed to represent /.snapshot/hourly.x/test?
WAFL makes a new copy of the block containing the inode to contain the
new version of the inode used by /home/test, leaving
/.snapshot/hourly.x/text with the older copy. Both have the same inode
number, but each is only accessible via its related file system version
path (which is similarly multi-versioned at the block level).
- bill
|
|
|
|
|