Defrag volume with DFS Share

[unknown]

I started a defrag (W2K defag) on a disk volume, that has a domain dfs root
and links----Mistake.
It looks as though the NTFS change log is indicating a file change, which
causes the NTFRS service to start replication. The FRS-Staging area fills
up rapidly and the defrag comes to a crawl.

This observed behavior seems to indicate that the NTFS file sys flags a file
sys change when the file is moved (as a defrag would do). I would have
expected that the metadata on the file would have enough resolution to
determine a file content change vs. a file move.

Is this a known glitch or oversight by the NTFS designers? I thought NTFS
was supposed to be an enterprise class file system??? This could cause major
headaches on a large deployment with numerous replicas on the other end of
WAN connections.

Does anyone know of any documentation that explains the file system in
detail?

Has anyone observed a similar behavior with third party defraggers?

Of all things, why isn't this documented?? I have spent a fortune on TechNet
an MS Books---I don't see anything about this..

I am presently running a virus scan on the same volume and see no FRS
activity, but maybe it needs to find a virus.

The defrag was stopped, NTFRS was stopped on all replicas, defrag
restarted --- finished quickly, the NTFRS was restarted----no problems
noticed.

TIA
Digital Doug

[Brendon Rogers]

http://www.microsoft.com/technet/itsolutions/techguide/msm/winsrvmg/fspog/fspog5.mspx#XSLTsection126121120120

http://support.microsoft.com/default.aspx?scid=kb;en-us;282791&Product=win2000

Post by unknown
I started a defrag (W2K defag) on a disk volume, that has a domain dfs root
and links----Mistake.
It looks as though the NTFS change log is indicating a file change, which
causes the NTFRS service to start replication. The FRS-Staging area fills
up rapidly and the defrag comes to a crawl.
This observed behavior seems to indicate that the NTFS file sys flags a file
sys change when the file is moved (as a defrag would do). I would have
expected that the metadata on the file would have enough resolution to
determine a file content change vs. a file move.
Is this a known glitch or oversight by the NTFS designers? I thought NTFS
was supposed to be an enterprise class file system??? This could cause major
headaches on a large deployment with numerous replicas on the other end of
WAN connections.
Does anyone know of any documentation that explains the file system in
detail?
Has anyone observed a similar behavior with third party defraggers?
Of all things, why isn't this documented?? I have spent a fortune on TechNet
an MS Books---I don't see anything about this..
I am presently running a virus scan on the same volume and see no FRS
activity, but maybe it needs to find a virus.
The defrag was stopped, NTFRS was stopped on all replicas, defrag
restarted --- finished quickly, the NTFRS was restarted----no problems
noticed.
TIA
Digital Doug