Docker volume n container out of sync after migration to new physical disk

while doing housekeeping of the storage space. i have to move the local storage to an external disk.
i mount the new volume and start copy files to new disk.

update the fstab to mount the new disk over the local folder thus keeping the same path.
start docker container without problem.
update file in the volume, but does not get reflected in the container.

if my understanding correctly, docker track volume and files inside by inode.
and with this simple migration exercise, it actually break the link of volume container relationship.
is this correct behaviour?

if answer is correct, then will like to know how we can do data migration which i believes to be very common in production situation.