Project

General

Profile

Bug #27760

Updated by Siegfried Beeh almost 3 years ago

Situation:
* Update to latest (=current) Version of FreeNAS 11 Stable Train. ZFS hasn't been updated.
* Network drive (on Windows PC) is connected to SMB service, with currently 3 active shares.
* All shares have several top-folders.

eg: P:\top-folder1
P:\top-folder2
P:\top-folder3
where P: is connected to a Windows-share that is connected to the a ZFS dataset /mnt/Vol1/shared/Eltern. dataset.
top-folder1...3 are just plain folders within the ZFS dataset.


Observation:
* A suspicious folder occurs besides the (valid) top-folders. e.g.
P:\suspiousfolder

This suspicious folder is named like a (previously) valid folder that has been existing at another location on the file system. It contains valid files/subfolders. But the folder is located at a very wrong place.
* Action: Moved that folder back to the original location. This was possible, but now another suspicious folder occurred at the same place within the top level
* Double-check on the command line shows, that the suspicious folder really exists at this location. So it is not only a visualization bug, it seems to be a bug that corrupts existing data.

Back