freshfeesh
Explorer
- Joined
- Oct 10, 2011
- Messages
- 72
[This is a repost of this, which I just realized is probably in the wrong forum]
About three weeks ago I re-imaged my compact flash Freenas boot drive to eliminate the possibility that some user configuration error was causing some network problems that I had already sunk a lot of time into. Happily, the error persisted, eliminating the user as the source of the network error. I'm writing now about a different error:
After reimaging, I autoimported the RaidZ1 array of (3) 3TB disks per plan. Everything was fine until I tried to run a sync, and every single file on Freenas was coming up with a "Date Modified" of 3 weeks ago, equal to the time I copied the files over to the array, rather than what should be, on average, about a year and a half ago. The sync software wanted to overwrite all files on other machines with the "newer" freenas files. I did the reimaging pretty soon after I first put the files onto the array, and I can't remember if I synced at all before I reimaged, i.e. I can't be sure that this problem has been caused by the autoimport, or at the time that I originally placed the files on the drive. However, when I place files onto the array now, date modified remains correct and unchanged. All other metadata on the files looks unharmed. Jpg's are by far the most common file type, but all file types are represented, and all exhibit the problem. These are CIFS shares shared with Windows machines only.
The more I think about this, the more I realize that this is a serious issue. I know that the latest versions of all my files still reside on other machines, metadata in-tact, so I can recreate the backup from scratch if necessary, this time. Any further down the line and I wouldn't have that luxury. My freenas server will be the center of a multi-machine setup. The location of the latest version of a file will arbitrarily be on either the freenas machine or one of the other machines, and the whole thing will depend on syncing to work. Were I to need to autoimport the array again, there would be no way to manually examine all the files from the various sources against the ones on the server. I would have to summarily discard one or the other.
Did I do something wrong? Is this a known failing? Is there a fix?
About three weeks ago I re-imaged my compact flash Freenas boot drive to eliminate the possibility that some user configuration error was causing some network problems that I had already sunk a lot of time into. Happily, the error persisted, eliminating the user as the source of the network error. I'm writing now about a different error:
After reimaging, I autoimported the RaidZ1 array of (3) 3TB disks per plan. Everything was fine until I tried to run a sync, and every single file on Freenas was coming up with a "Date Modified" of 3 weeks ago, equal to the time I copied the files over to the array, rather than what should be, on average, about a year and a half ago. The sync software wanted to overwrite all files on other machines with the "newer" freenas files. I did the reimaging pretty soon after I first put the files onto the array, and I can't remember if I synced at all before I reimaged, i.e. I can't be sure that this problem has been caused by the autoimport, or at the time that I originally placed the files on the drive. However, when I place files onto the array now, date modified remains correct and unchanged. All other metadata on the files looks unharmed. Jpg's are by far the most common file type, but all file types are represented, and all exhibit the problem. These are CIFS shares shared with Windows machines only.
The more I think about this, the more I realize that this is a serious issue. I know that the latest versions of all my files still reside on other machines, metadata in-tact, so I can recreate the backup from scratch if necessary, this time. Any further down the line and I wouldn't have that luxury. My freenas server will be the center of a multi-machine setup. The location of the latest version of a file will arbitrarily be on either the freenas machine or one of the other machines, and the whole thing will depend on syncing to work. Were I to need to autoimport the array again, there would be no way to manually examine all the files from the various sources against the ones on the server. I would have to summarily discard one or the other.
Did I do something wrong? Is this a known failing? Is there a fix?