247 reputation
210
bio website
location Los Angeles, CA
age
visits member for 3 years, 7 months
seen Sep 14 at 8:22

1d
awarded  Popular Question
Jan
28
comment Alternative to diff with progress for massive directory compare?
diff gives me results in the form of "Files __ and ___ differ" ... and I'm running that through sed -e "s/Files /cp -afv /" -e "s/ and / /" -e "s/ differ$//" to try and generate a script for re-copying the bad files. But diff's output is unquoted, so it doesn't work. Can I get it to give me quoted paths?
Jan
28
comment Alternative to diff with progress for massive directory compare?
Yes, but diff doesn't copy ... it just reads both files; while rsync, to copy, must read each byte, then write it. This was an rsync from scratch, so it was copying every file.
Jan
28
comment Alternative to diff with progress for massive directory compare?
If I run rsync -vin -- does that do a byte-by-byte or checksum comparison? I thought rsync only compared size/date unless you add -c. And from what I've read the speed large files seems to only make a difference with non-binary files ... or am I wrong?
Jan
28
comment Alternative to diff with progress for massive directory compare?
What does that do exactly?
Jan
28
comment Alternative to diff with progress for massive directory compare?
I'm also confused as to why rsync copied the data at around 150MB/s, yet diff compares at only 60MB/s ... ?
Jan
28
awarded  Commentator
Jan
28
comment Alternative to diff with progress for massive directory compare?
Is there a way to get it to mv every file it finds to a "verified" folder at the root of the drive, preserving the full path? E.g., if /disk1/a/b/c/file1 is identical to /disk2/a/b/c/file1, then move it to /disk1/verified/a/b/c/file1. Then I could end up with only the badly copied files. (So far LOTS of files over 10GB are not verifying, which is scary.)
Jan
28
asked Alternative to diff with progress for massive directory compare?
Oct
30
asked Best flavor of Linux for an Acer Revo 3600 as media server?
Oct
26
awarded  Notable Question
Feb
22
awarded  Popular Question
Jan
7
awarded  Nice Question
Jan
4
awarded  Popular Question
Aug
28
awarded  Yearling
Aug
28
revised (Mac Terminal) sed to parse JSON … what am I doing wrong?
edited for Mac compatibility
Aug
28
suggested suggested edit on (Mac Terminal) sed to parse JSON … what am I doing wrong?
Aug
28
revised (Mac Terminal) sed to parse JSON … what am I doing wrong?
added 17 characters in body; edited title
Aug
28
accepted (Mac Terminal) sed to parse JSON … what am I doing wrong?
Aug
28
comment (Mac Terminal) sed to parse JSON … what am I doing wrong?
@Kevin AHA! That did it! Thanks! | sed 's/^.*"name":"\([^"]*\)".*$/\1/'