![]() ![]() Looking at the console for the logs we saw that there was an error saying 'fsmpm not started' (which was slightly cryptic).Īnyways long story short, we needed to add an additional IP address to our NICs for the metadata network (10.0.10.x) and then everything played nicely. However, when the system tried to mount the volume it came up with a very non descriptive error. ![]() When attempting to create the volume we were then able to allocate the LUNs to the tags (note: don't name your meta data LUN 'metadata' - the system doesn't seem to like that) and go ahead and create the volume. We blew the RAID configurations away and re-allocated the RAIDs as detailed above. Here's what I did to resolve the issue - it was, more or less, a requirement for patients. HD Video configuration (Metadata/Journal, Video, Audio and Other tags). ![]() In regards to the LUN tagging for the storage pools we have the following planned: QMatic nodes and regular workstations will access the data over AFP shares, though if the QMatic machines are experiencing bottlenecks with disk access we can upgrade them to be attached via the Fabric. The Edit Suites will be direcly attached to the SAN via Fiber on the same fabric as the servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |