FSAssets Service - Revision history

Manni at 14:37, 9 April 2026

2026-04-09T14:37:52Z

Tampa: /* FS Assets */ Document the format change

2022-12-09T08:33:02Z

‎FS Assets: Document the format change

Manni: /* FS Assets */

2021-01-21T09:18:28Z

‎FS Assets

Ferd Frederix: /* Migration */ Add timeout parameter for large blog issues and timeouts

2021-01-20T22:18:47Z

‎Migration: Add timeout parameter for large blog issues and timeouts

Acryline at 14:52, 24 November 2015

2015-11-24T14:52:32Z

AliciaRaven: /* Hypgergrid Assets */

2015-08-05T16:17:36Z

‎Hypgergrid Assets

AliciaRaven: /* FS Assets */

2015-08-05T16:17:08Z

‎FS Assets

Melanie: /* Config Options */

2015-07-30T21:52:34Z

‎Config Options

AliciaRaven: /* Migration */

2015-07-30T21:00:21Z

‎Migration

AliciaRaven: /* Migration */

2015-07-30T20:42:16Z

‎Migration

@@ Line 2: / Line 2: @@
 =FS Assets=
 FSAssets is intended for grids where the size of the database is expected to exceed 50GB. This option will save the assets to the file system as opposed to the default service which stores assets as blobs in the database. This option also provides deduplication abilities, each asset is hashed when it is received for storage and if the asset already exists, the asset service will link to the existing file rather than store two copies.
 ==Config Options==
@@ Line 17: / Line 26: @@
   ;FallbackService = "OpenSim.Services.AssetService.dll:AssetService"
   ;DaysBetweenAccessTimeUpdates = 30
   ;StorageProvider = ""
@@ Line 23: / Line 34: @@
   ;UseOsgridFormat = false
 * '''BaseDirectory'''
@@ Line 32: / Line 45: @@
 * '''DaysBetweenAccessTimeUpdates'''
 ::By default, the access time is updated each time an asset is requested. This option can be used to skip this update for assets that already have a recent access time and reduce calls to the database.
 * '''StorageProvider'''
 ::To change where the metadata is saved you can set a specific storage provider and connection string. If this is disabled, the default storage provider given in the database section will be used to save metadata.
@@ Line 40: / Line 57: @@
 * '''UseOsgridFormat'''
 ::Changes the folder structure from 00/00/00 to 000/000 for compatibility reasons. False means 00/00/00 which is encouraged.
 ==Migration==
-While FSAssets will use the FallBackService if set, to convert any existing assets when they are requested and not found, this will not automatically convert all the old assets to the new service. To convert all assets from the default service there is a console command provided:
+While FSAssets will use the FallbackService if set, to convert any existing assets when they are requested and not found, this will not automatically convert all the old assets to the new service. To convert all assets from the default service there is a console command provided:
 <pre>
   import <conn> <table> [<start> <count>]
@@ Line 52: / Line 73: @@
 Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.
-If the import command fails with a timeout error., add "command timeout=300;" to the connection string:
+There is also a force import mode that overwrites existing content for matching asset IDs:
 <pre>
@@ Line 58: / Line 85: @@
 </pre>
-The timeout is in minutes, and the default is only 30 seconds.
+Timeout units and defaults depend on the database provider/driver. In most setups this value is interpreted as seconds.
 ==Hypergrid Assets==
@@ Line 66: / Line 102: @@
    LocalServiceModule = "OpenSim.Services.HypergridService.dll:HGFSAssetService"

@@ Line 21: / Line 21: @@
   ;ConnectionString = ""
   ;Realm = "fsassets"
 * '''BaseDirectory'''
@@ Line 36: / Line 38: @@
 * '''Realm'''
 ::The table name to save metadata in the database. Default is 'fsassets'
 ==Migration==

@@ Line 1: / Line 1: @@
 {{Languages|FSAssets_Service}}
 =FS Assets=
-FSAssets is intended for larger grids where the size of the database is expected to exceed 50GB. This option will save the assets to the file system as opposed to the default service which stores assets as blobs in the database. This option also provides deduplication abilities, each asset is hashed when it is received for storage and if the asset already exists, the asset service will link to the existing file rather than store two copies.
+FSAssets is intended for grids where the size of the database is expected to exceed 50GB. This option will save the assets to the file system as opposed to the default service which stores assets as blobs in the database. This option also provides deduplication abilities, each asset is hashed when it is received for storage and if the asset already exists, the asset service will link to the existing file rather than store two copies.
 ==Config Options==

@@ Line 47: / Line 47: @@
 </pre>
 Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.
 ==Hypergrid Assets==

← Older revision		Revision as of 14:52, 24 November 2015
Line 1:		Line 1:
		+	{{Languages\|FSAssets_Service}}
	=FS Assets=		=FS Assets=
	FSAssets is intended for larger grids where the size of the database is expected to exceed 50GB. This option will save the assets to the file system as opposed to the default service which stores assets as blobs in the database. This option also provides deduplication abilities, each asset is hashed when it is received for storage and if the asset already exists, the asset service will link to the existing file rather than store two copies.		FSAssets is intended for larger grids where the size of the database is expected to exceed 50GB. This option will save the assets to the file system as opposed to the default service which stores assets as blobs in the database. This option also provides deduplication abilities, each asset is hashed when it is received for storage and if the asset already exists, the asset service will link to the existing file rather than store two copies.

← Older revision		Revision as of 16:17, 5 August 2015
Line 46:		Line 46:
	</pre>		</pre>
	Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.		Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.
		+
		+	==Hypgergrid Assets==
		+	If your grid has hypergrid enabled, you probably have it setup to use the HGAssetService for sharing assets with other grids. In this situation you will need to change the HGAssetService section of your Robust.ini to point to the FSAssets version of the HGAssetService known as HGFSAssetService.
		+
		+	To enable the HGFSAssetService, find the HGAssetService section of your Robust.ini, the LocalServiceModule should be changed to:
		+
		+	LocalServiceModule = "OpenSim.Services.HypergridService.dll:HGFSAssetService"

@@ Line 24: / Line 24: @@
 ::This is the folder in which the asset data will be saved.
 * '''SpoolDirectory'''
-::The spool directory is a folder used for temporary storage while the asset is hashed and compressed before it gets moved to the BaseDirectory. This should be on the same file system as the base directory.
+::The spool directory is a folder used for temporary storage while the asset is hashed and compressed before it gets moved to the BaseDirectory. This must be on the same file system as the base directory.
 * '''FallbackService'''
 ::If you are upgrading from the default asset service, uncomment this and set the default asset connector. This will allow FSAssets to retrieve an existing asset from the old service and add it to the BaseDirectory. The fallback service is checked when an asset is requested but not found by FSAssets.

@@ Line 38: / Line 38: @@
 ==Migration==
 While FSAssets will retrieve and convert an existing assets when they are first requested using the 'FallBackService' if available, this will not automatically convert all the old assets to the new service. To convert all assets from the default service there is a console command provided:
+<pre>
   import <conn> <table> [<start> <count>]
+</pre>
 The import command expects a database connection string and the name of the legacy asset table to be passed as parameters. The following example shows how to start the import process for a MySQL database, just change the connection details to match your database schema, username and password:
+<pre>
   import "Data Source=localhost;Database=SCHEMA;User ID=USER;Password=PASS;Old Guids=true;" assets
+</pre>
 Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.