just wondering if this is the intended way for this to work or what:

 

i have enabled user shares, and one of the shares is called HD-DVDs which is spanned across i think 4-5 drives right now.  I'm exporting it as read-only.  Now, when I add a new movie, to lets say disk1/hd-dvds, the HD-DVDs share does not update, it does not show the new movie that I added to the drive.  Same thing happens if I happen to change a folder name (for example 300 HDDVD to 300 HD-DVD), the update does not take place.  If I stop the array and restart it, the changes are now shown in the HD-DVDs share, the new movie and the folder name change now show.

 

So i decided to just create a new empty folder under disk1/hd-dvds, and it showed up fine in the HD-DVDs share w/o needed a restart of the array...

 

so whats up with this....any reason you can think of?

 

thanks

ok so this happens in the HD-DVDs share and not the DVDs share. I created a couple new folders disk4/dvds (has regular ripped dvds) and both folders showed up in the user share and showed all movies across all drives.

I created a couple new folders on disk4/hd-dvds and none of the new folders showed up in the user share, still had the old movie list and not including the new folder i just created

with the writable user shares, new files/folders created in the individual disk shares for a SPANNED user share will not show up until a restart. I believe adding the "rescan" button back to the user intervace is in the plan for the next release. If you create a file or folder in a disk share for a SINGLE DISK user share, it will show up. This is because, as I understand it, the spanned (multi-disk) user shares a kept in the ram disk, the single disk user shares are direct read from the disk.

 

So, the HD-DVDs share exists on several drive, and writing to the say Disk4/HD-DVDs directory will not showup until a restart. The DVDs share is only on disk 4, is that correct? if so, that's why you see new folders on that share immediately.

 

HTH

cmhardwick,

 

yes you are correct, and thank you for the explanation!