| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 646.1 | it depends | DECWET::SDY | Look out!!..Support Rookie sez... | Thu May 01 1997 12:58 | 19 |
|
If you don't have HSM running on the NFS client, what happens is that the client
will see a soft-link to a non-existant file. Usually the client will get read
errors and terminate as if it were not accessible.
The scenerio you propose, would still save space on the (NFS) server, however
you'd have to have an HSM client touch the file, before anyone else could
actually see it. Personally, I don't know many users that would stand for this
on a regular basis. If, instead it's really an "accident" that a non-HSM client
tried to access the file and that the only people who should be accessing the
files, would normally be running the HSM client, then it might actually work ok.
I don't know what a LAN Manager client does with a "dead" soft-link. We don't
have it running here to test. Easist thing to do would be to create a soft link
to a file, delete the file and then see what LAN Manager does.
steve.
|
| 646.2 | | PRIME8::VAUGHN | Mike Vaughn DTN 339-5325 | Thu May 01 1997 13:28 | 11 |
| Thanks for the quick response. A little clarification, please.
Are you saying that a non-HSM client "touching" an archived
file (i.e., the soft link) will or will not cause the file to
be restored? I can see no way around the error message, but I was
wondering if I "tried again in 3 minutes" if the file might not be
restored.
What do you think?
mike
|
| 646.3 | sorry, no easy NFS access... | DECWET::SDY | Look out!!..Support Rookie sez... | Thu May 01 1997 13:54 | 10 |
| An NFS (only) client, will not cause a file to be recalled on an NFS/HSM server.
The only thing the (NFS) client can do is to delete, or rename the link.
How to accompilish this is better documented in the release notes, but basically
you need HSM clients to de-migrate HSM migrated files.
The "try again in a few minutes" release note, is about potential NFS timeouts
not being handled nicely by the NFS/HSM client.
steve.
|
| 646.4 | | SANITY::LEMONS | And we thank you for your support. | Thu May 01 1997 14:53 | 9 |
| .1> If you don't have HSM running on the NFS client, what happens is that
.1> the client will see a soft-link to a non-existant file. Usually the
.1> client will get read errors and terminate as if it were not accessible.
Hmm. The NFS client will be requesting services of an NFS server. If
that NFS server runs on a node that is also running HSM, then would all
be well?
tl
|
| 646.5 | one would think so, but that would be wrong....in Legato's eyes. | DECWET::SDY | Look out!!..Support Rookie sez... | Thu May 01 1997 18:17 | 13 |
| > Hmm. The NFS client will be requesting services of an NFS server. If
> that NFS server runs on a node that is also running HSM, then would all
> be well?
since accessing the soft link is only recognizable by a special (HSM client) NFS
daemon, doing a normal NFS access (via the system NFS server) has no effect
w.r.t. the de-migration of the file. I know this sounds counter-intuitive, but
it's actually the local (client side) touching of the link that spawns off the
recall of the file from the remote HSM server. Hence, if the client doesn't have
the HSM index browser daemon (nsrib) running locally, there is no way for the
client to request the recall of the file from the server.
steve.
|
| 646.6 | | PRIME8::VAUGHN | Mike Vaughn DTN 339-5325 | Fri May 02 1997 08:17 | 4 |
| Oh well. Not exactly what I was hoping for, but thanks for describing the issue so
clearly.
mike
|
| 646.7 | also see the HSM FAQ, for a short, direct answer to the question | DECWET::CARRUTHERS | Life gets easier when you realize you can't have everything. | Fri May 02 1997 10:56 | 2 |
| or if you read the FAQ and now have a suggestion for how it's answer
may be improved, please pass it along ....
|