Rename with Multiple User Handles

NTFSD
1

Assuming all the access rights are correct, can someone give me answer to
the following?

– Thread A opens file OLD_NAME.
– Thread B opens file OLD_NAME, performs a rename operation from OLD_NAME
to NEW_NAME, and then closes the file.
– Thread C attempts to open file NEW_NAME.

Will the attempt to open file NEW_NAME by Thread C succeed without Thread A
first closing it? Thread B opened OLD_NAME for the rename operation with
FO_WRITE_THROUGH, if that matters. And this happens to be the fully
qualified rename case, with ReplaceIfExists FALSE, which probably doesn’t
matter either.

Thanks,

R. Auerbach

2

Russ,

Is Thread C opening it in a manner that is compatible with how Thread A has
opened it? In general, if it does, I’d expect it to successfully open it.
Of course, a specific file system might decide to implement different
semantics, but it wouldn’t seem intuitive.

Regards,

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Russ Auerbach [mailto:xxxxx@ENGENIA.COM]
Sent: Wednesday, July 12, 2000 3:21 PM
To: File Systems Developers
Subject: [ntfsd] Rename with Multiple User Handles

Assuming all the access rights are correct, can someone give me answer to
the following?

– Thread A opens file OLD_NAME.
– Thread B opens file OLD_NAME, performs a rename operation from OLD_NAME
to NEW_NAME, and then closes the file.
– Thread C attempts to open file NEW_NAME.

Will the attempt to open file NEW_NAME by Thread C succeed without Thread A
first closing it? Thread B opened OLD_NAME for the rename operation with
FO_WRITE_THROUGH, if that matters. And this happens to be the fully
qualified rename case, with ReplaceIfExists FALSE, which probably doesn’t
matter either.

Thanks,

R. Auerbach

You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)