Jason Gerard DeRose added the comment:
vajrasky, one more errno to consider:
[Errno 39] Directory not empty: '/tmp/bar'
This is when renaming a directory: src directory exists; dst directory exists
and is non-empty.
In 3.4 Beta1, this error message now includes the src instead
New submission from Jason Gerard DeRose:
Under Python 3.3, if renaming a directory with `os.rename()` when the
destination is an existing, non-empty directory, like this:
os.rename('/tmp/foo', '/tmp/bar')
You'll get an OSError with a message like this:
OSError: [Errn
Jason Gerard DeRose added the comment:
Oops, I think I don't understand the meaning of top CPU usage, as time tells a
different story.
Direct ext4:
real2m14.144s
user0m0.260s
sys 0m30.350s
ecryptfs over ext4:
real8m47.130s
user0m0.080s
sys 7m2
Jason Gerard DeRose added the comment:
Barry,
I'm suspicious there might be more to the performance issue than just the
ecryptfs overhead. While experimenting with a read benchmark, I just happened
to notice that when reading from an ecryptfs filesystem, the CPU usage is
unusually hi
