| Issue 60: | Definition of ONLINE | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Hello everybody, I have still not got the idea of "online" HSM properly. Can SKS and RV write a justification of "How OHSM is online when writes and reads hanged up"?
Feb 3, 2009
Project Member
#1
sandeepksinha
Feb 3, 2009
Can you clarify a little more on namespace changes? As in, how would you define a namespace in this context? Any reason why the stubs used in HSM slow the data path? Curiosity didn't kill the cat. It made it wiser :)
Feb 3, 2009
Namespace here means... in your code if you have written fopen($MNTPT/a.c); Things like this is written so that when you mount the same device somewhere else and compile, automatically it should compile with the current mountpoint. But once you change the mount point by copying the data to other mountpoint. Applications will break, It basically means change in the path name. The stubs slows down means... Its juts like the idea where you create a new inode and relocate the data there. What you do to the original inode is that "All read/write" will first restore the data blocks and then perform the i/o. Making it slower. So stubs means you add a dummy code which does the actual work along with what you want to,
Feb 3, 2009
(No comment was entered for this change.)
Summary:
Definition of ONLINE
Feb 3, 2009
The explanation is quite good and satisfying. RV take a note of this. This is your job to convince the public that we are ONLINE.
Feb 3, 2009
(No comment was entered for this change.)
Status:
Done
|