search for: creating_sparse_fil

Displaying 3 results from an estimated 3 matches for "creating_sparse_fil".

Did you mean: creating_sparse_files
2020 Jan 15
4
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
Hi all, I'm writing a script that uses rsync to sync 2 dirs on C7. I noticed a strange behaviour. I have 2 dir: src and dest. In src dir I generate a testfile with "dd if=/dev/zero of=testfile bs=1M count=100" and when I run "du -h testfile" I get the correct result. Then I sync src/ to dest/ using "rsync -avS? src/ dest/", all ok but when I run "du -h
2020 Jan 15
0
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
...ng -S > (--sparse) from rsync command problem does not occour. > In another test, thinking about a problem on 0ed file, I tried file > generation using /dev/urandom then /dev/zero and running rsync -avS the > problem is disappeared. > https://wiki.archlinux.org/index.php/Sparse_file#Creating_sparse_files In short, rsync is being told to create sparse files with the -S flag, so it does. Could you share what you did with the urandom then zero test you mentioned? I'm curious what exact sequence of commands you used.
2020 Jan 15
2
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
...) from rsync command problem does not occour. >> In another test, thinking about a problem on 0ed file, I tried file >> generation using /dev/urandom then /dev/zero and running rsync -avS the >> problem is disappeared. >> > https://wiki.archlinux.org/index.php/Sparse_file#Creating_sparse_files > > In short, rsync is being told to create sparse files with the -S flag, so > it does. Could you share what you did with the urandom then zero test you > mentioned? I'm curious what exact sequence of commands you used. > _______________________________________________ > C...