What "the larger number" are you referring to? Should I set bs=16384kB as the disk cache size rather than the larger number to maximize the speed? One is conv=sync and the other is iflag=sync. Note that there are two sync options available with dd. Raw disk sectors cannot be presumed to have any such integral sequence numbering, and require padding to try to preserve the integrity of the copied filesystem. If you were using dd to copy blocks that had an integral sequence number, then padding might not be necessary to detect or account for missing blocks. Or if the subsequent data skipped over the destination sectors corresponding to the errors (or did a seek (in dd parlance) to its corresponding sector), then the garbage data in those skipped-over sectors would be treated as copies of original data. If the input buffer is not padded to account for the sector(s) that is/are unreadable, then the subsequent data that are written will be offset from the proper sectors that they should be written to. However when "continue after read errors" is specified, the lack of data is then an issue. If dd terminated on such an error (as it normally would), then the lack of data is not an issue. The disk controller provides no sector data for the input buffer when a hard (i.e. This option that can add padding is necessary when also specifying the noerror, or "continue after read errors", option. Pad every input block with NULs to ibs-size when used with block or unblock, pad with spaces rather than NULs Per the Linux man page Each CONV symbol may be: If you're going to use the conv=noerror option, then you had better use the conv=sync with it, or you might end up with a useless backup. Permanenter Link des Eintrags.Should I add sync option as suggested? tar.bz2 of course.įeel free to add your file transfer quick hack here.ĭieser Eintrag wurde veröffentlicht in Allgemein, CommandLine, FileTransfer, Netcat, Network, Tar, Ubuntu von ccm. If you use something like gzip or bzip2 compression you should choose something like. Please note that on the receiver side you are completely free to choose a file name for the. You just setup a very fast file transfer. $ nc -w 10 remotehost 7878 > nameoftar.tar For convenience he also sets a timeout parameter (-w 10): The receiver has to call netcat and tell him to connect to the remote machine and the correct port and redirects the standard output to a file. Netcat is told to start in server mode (-l), listen on port 7878 (-p 7878) and shutdown itself after waiting 10 seconds after having seen an end of file in standard input (-q 10): The next line tells tar to build a tarball and write it to standard output which is redirected via a pipe to netcat. The sender has to call netcat in server mode and pipe content into it. I will just show you how to use it without compression for a directory. A very simple and even cross platform solution is using netcat and in case of a directory in combination with tar like the following steps. Both computer owners are just to lazy to setup something like ftp, smb, nfs. Imagine you are on lan party or on the road and quickly want to transfer a file or directory to another computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |