Comment # 4 on bug 1068647 from
One possibility to overcome the send problem would be simply ignoring orphan
inodes in the code path indicated in comment 1 (finish_inode_if_needed() ->
send_utimes()). I don't see how that would cause harm. Maybe send would bail
out later if it hits the ORPHAN entry in the FS tree?


You are receiving this mail because: