The exception of getting an understandable message is when gstat can not find firebird.msg or interbase.msg. Here, you see ODS number 32779 – this is encoded 11, with the high bit added since Firebird 2.0 (in hex it will be 800B, where B = 11), to avoid confusion between InterBase and Firebird databases, because from some point they had equal ODS number, but very different database format. If gstat will not understand read information, it will show corresponding message – what it expected, and what it found.įor example, if we run gstat from InterBase 4 at database from Firebird 2, it will show Wrong ODS version, expected 8, encountered 32779?
#DISK AID FILE TRANSFER PASSWORD#
User and password here unnecessary, because gstat with –h option just read physical part of the database (header page, number 0). You can find out ODS of your database running the following command gstat –h database_file_name But there are some limitations, which will be described further. This allows the server to work with database files from previous versions and simplify the transition from the old server to a new one. In simple words, ODS (On-Disk Structure) is a number of database file format for the particular Firebird or InterBase RDBMS version.Īlmost all versions use so-called “Y-valve” to support current ODS and some old ODS. I assume again, there is some smart way of doing this, but have been unable so far to find a solution.All Firebird and InterBase On-Disk-Structure (ODS) versionsīy Dmitry Kuzmenko, 2 What is On-Disk Structure (ODS) Number
The main challenge that I am facing is the ability to calculate the total progress for this I need to extract the current transferred number of bits. Total_size=$(du -sb /home/agco/ros_bags/| cut -f1)ĭd if=$i status=progress bs=64M of=/media/upload_disk/$(basename $i)
I have started writing a sh script that uses dd instead: #!/bin/sh I could make a script that uses dd to copy all the files individually and at the same time monitors the progress,Įither using rsync or some other standard linux tool. In this case, I am using a similar block-size to rsync, to ensure they are as similar as possible. I get transfer speeds in the range of 500-600MB/s for the same setup. When I use dd to copy the individual files: dd if=/home/user/rosbags/-12-22-33.bag bs=131K status=progress of=/media/upload_disk/-12-22-33.bag My assumtion is this should be similar to what one with get with a direct copy, but I could have misunderstood the settings. Since I use the -W (whole file) setting it should use normal transfer and not delta compression. I specificly set the blocksize to the max value, to ensure this i not the limiting factor. It seems to be helping to change the protocol in rsync to version 29 or earlier with 15-20% additional MB/s.
This gives me a transfer speed of 150-180MB/s and I get a total progress for all files that need to be transfered. I started out with rsync and found the following to provide the best speed result: rsync -W -size-only -protocol=29 -block-size=131072 -no-compress -info=progress2 /home/user/rosbags/*.bag /media/upload_disk/ I would like to monitor the overall progress for the transfer of all files and have a fast transferspeed to the USB disk. The files I need to transfer are in the range of 5-200GB. I need to transfer a number of large files of specific types from an internal disk to an USB SSD drive.
0 kommentar(er)
