This includes :
  - merge of d2dtransfer into diskmanagerd
  - drop of the WAITDISKTODISKCOPY state in DiskCopy, and of the diskcopies for ongoing replication in general. Now DiskCopies are only created at the end of the replication, when they actually exist on disk
  - drop of the StageReplicaRequest table and concept
  - introduction of the DiskToDiskCopyJob table, holding the list of ongoing disk to disk copies
  - a split of transferToSchedule into userTransferToSchedule and D2dTransferToSchedule
  - an according split in the dispatcher part of the transfer manager to call both methods. Note that with this commit, both methods fill the same FIFO queue of transfers and both take everything they can find without any throttling.

At this stage, the draining facility is broken.

Fixed in the trunk.

Bug #101372: Incorrect cleaning of old requests leading to wrong final reported statuses of repack -s

Fixed archiving step after a repack abort.

Bug #95189: Time discrepencies between disk servers and name servers can lead to silent data loss on input

- Properly use cns_file_metadata.stagertime as a single time source for stager open/close operations.
This included modifying a server-side data structure, Cns_file_metadata, and the semantics of
openx() and closex() along with their wire protocol: thus after this change only a new stager can
talk to a new nameserver (i.e. no backwards- nor forwards-compatibility provided).
- Introduced a CastorConfig table in the db with one configuration parameter, openmode, to decide
whether to use the old 'Compatibility' mode as before or the 'New' mode as described above.
- On the way, proper filling of cns_seg_metadata's creationtime, lastmodificationtime and gid fields has
been implemented for logging/statistical purposes.

Merged STAGED and CANBEMIGR into VALID in DiskCopy statuses and create a tapeStatus on the CastorFile with possible values NOTONTAPE, ONTAPE and DISKONLY.
Note that user interface is not touched and still displays CANBEMIGR and STAGED. Only internals (particularly the DB) are concerned.

Fixed bug #101344: CASTOR should not try to create new copies of ARCHIVED, DISABLED and EXPORTED tape copies

as OK to be dropped. This state will eventually disappear
but for now it needs to be taken into account.

Implemented a new tool, deletediskcopy, to replace cleanLostFiles
and provide all features described in the above bug and its related ones.

- Introduced support for a READONLY state for Diskservers and Filesystems.
Hardware in such a state will accept migrations, [PrepareTo]Get and
DiskCopyReplica requests, and will not accept recalls or [PrepareTo]Put/Update
ones when they switch to write mode.
- Dropped the {DiskServer,FileSystem}.adminStatus fields and the obsoleted
code around them and introduced a new DiskServer.hwOnline boolean field, which
is updated by the heartbeat reports and displayed by printdiskserver.
In turn, modifydiskserver can not change the online flag but only the status.
For backward compatibility, on stager_qry -s a Diskserver will be reported
as DISABLED if hwOnline = 0 regardless its status.

bug #95189: Time discrepencies between disk servers and name servers can lead to silent data loss on input

Properly update the lastUpdateTime on the stager on write operations,
now that it is used to double check for concurrent modifications.
For the moment read operations are ignored as explained in the comment.

integration of the monitoring of diskserver statuses in the diskmanagerd/transfermanagerd infrastrucutre. In particular rmmasterd, rmnoded and all the shared memory infrastructure have now disappeared

Handled case of a lastKnownFileName already in use when fixing lastKnownFileName in FileRenamedCleanup

used for long, this is only to cleanup and make the code clear.

Fixed bug #98151: Do not try to recall a diskonly file. Also improved logging of cases where we do not find any segment for a file that should be recalled. Distinguish the case with no segment at all (logged a critical, with note that the file is lost) and the case where all segments are disables (warning only). Also list all disabled segments in the log with the reason for their unavailability (segment status and tape status)

Plus fixed some errors introduced in recent refactoring commits...

Plus added some code in abortRepack to catch exceptions and reset the state
before raising them to the user.

Added hints for draining and checking when filesystem come back in production, following optimization session with repack

Fixed bug #98250: Incorrect loop in archiveOrFailRepackSubreq leading to PL/SQL: numeric or value error.
Fixed also a few more occurrences of FIRST..LAST, even though
it appears the logic around wouldn't have led to the bug.

Fixed problem introduced with last commit leading to Oracle errors when no request is processed.

Fixed bug #98072: files not dropped on disk on aborts + played safer when failing d2d transfers to avoid the same kind of problems

Added new GCTYPE_OVERWRITTEN constant and used it in recreateCastorFile
to catch when files get overwritten.
Side refactoring: all GCTYPE constants were renamed and added to the dconst package,
as well as all draining processes specific constants.