nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to activate a NFS mount as a content store

Amlan

Hi All,

We are not able to activate the content stores in the TeamSite 6.7.1 server in . The initial checks suggest that we cannot activate content stores if the directories are already mounted. If we create a directory within /iw-store and try to activate it, it works without any issues. Please can you provide us some pointers on the same?

Example:

When we try to activate the store /iw-store/xyz and if directory is mounted(NFS Share) we get an error

Unable to activate store: I/O error

We are using TeamSite 6.7.1 on a T2000 machine

Please can somebody provide me some pointers

Regards,
Amlan

Find more posts tagged with

Comments

drew1

It sounds as if you are nfs mounting a backing store directory on the iw-store directory. There's no need to have all backing stores exist in the iw-store directory.

For example, to add a backing store that's mounted on a remote nfs share:

mount remote-host:/share/teamsite /remote
add to iw.cfg in the [iwserver] section:
store_directory_store1=/remote/teamsite/store1
iwstoreadm -a store1

Also make sure that the TeamSite user has permission to access the remote nfs share.

Amlan

Hi Drew,

Thanks for your reply. I think we have found the solution to the problem. It seems that TeamSite doesnt allow us to create a content store if the folder is not empty initially. There is a file .snapshot within the NFS mounted directory which prevent us to activate the directory as a content store.We tried to create a content store normally and copied the contents to the NFS shared folder and then tried to activate it and it worked.

Is this something that you are aware of because it is strange. I think it is a bug from interwoven.Your thoughts on this?

Regards,
Amlan

beez

Yes. Store initialization will fail if you specify a backing store directory that is non-empty.

This is the simplest way of preventing the case where you accidentally initialize a store on top of an old one, which can result in *major* problems.

--Beez

Amlan

Hi Beez,
I agree with you, but then how can we activate the store by copying the contents of an existing store into it?

Example:
We have an existing store "A". We copy the contents of "A" into a non-empty directory "B" and try to activate "B" and it works.

Your thoughts on this?

Regards,
Amlan

beez

When I said "Store initialization will fail" I meant that when you ask TeamSite to create a brand new store, it will fail if you are telling it to create the store in a non-empty directory.

You are free to copy an existing store to a non-empty directory, tell teamsite where this store is, and then start-up the store with iwstoreadm -a . In this case, TeamSite doesn't care that there are extra files in the directory. However this is NOT a recommended practice because the pre-existing files may cause problems later on (depending on their names).

--Beez

Amlan

In our case, we seem to have no other issue but to create a temporary store and copy the contents to the our stores. Will this create problems later on as the temporary store has never been used. Are there specific name mappings within the content stores that may create a problem later on

Regards,
Amlan

beez

In our case, we seem to have no other issue but to create a temporary store and copy the contents to the our stores. Will this create problems later on as the temporary store has never been used. Are there specific name mappings within the content stores that may create a problem later on

Regards,
Amlan

You should be ok. Just make sure the directory only contains the .snapshot file you mentioned and no TeamSite files.

The *worst* thing you can do is to copy a store on top of another. This is what we are trying to prevent by disallowing the creation of a brand new store in a non-empty directory.

--Beez

Amlan

Ya , we have made sure of that. Thank you for your inputs

Regards,
Amlan