October 16, 200718 yr Did the ability to re-scan user shares manually go away with 4.2? If so, how to I get files that I write directly to the disk shares to show up in the user shares (or do they show up automatically after writing is complete or some period of time)? I have one drive that mis-behaves if I try to write anywhere over the 260GB mark oro so so I leave it half full and just fill up the other drives (otherwise I'd be able to write to the user share directly and use high-water).
October 16, 200718 yr Author Never mind, once the movie finished ripping it showed up in the user share right away - sweet. Apparently 4.2.1 also fixed the problem that was happening with the other drive as well so I recovered 240GB of storage :-)
October 16, 200718 yr Never mind, once the movie finished ripping it showed up in the user share right away - sweet. Apparently 4.2.1 also fixed the problem that was happening with the other drive as well so I recovered 240GB of storage :-) Whether a file shows up in a User Share after creating directly in a disk share depends on the what directory the file is created in. If it's created in a "spanned" directory, ie, one one exists on multiple disks, then it will not appear in the user share unless you stop/start the array. If it's created one level 'down' from a spanned directory, then it will show up. We added back the 'Rescan' button for the next release.
October 17, 200718 yr will the Re-Scan still bring the Samba daemon, killing the shares momentarily? Seems someone posted that there was a way to update the shares without doing this.
Archived
This topic is now archived and is closed to further replies.