On 27.05.2013 09:59, Tobias Bading wrote: > Quick update: > The problem is definitely timestamp related. "touch 3449_spurious" > fixes a "corrupt" working copy, i.e. "svn status" and "svn diff" work > properly afterwards. I'll try to figure out why my machine is living > in its own timeline. All I can say after reading just a few lines of > python code is that I don't have > SVN_I_LOVE_CORRUPTED_WORKING_COPIES_SO_DISABLE_SLEEP_FOR_TIMESTAMPS > hard-wired to 'yes' :-).
Well, that's a relief, at least. Can you please get two pieces of information: 1) run the "mount" command and past the line representing the ext4 filesystem where your working copy lives 2) Get the ext4 superblock info, using "sudo tune2fs -l /dev/something"; the mount output will tell you which /dev/something -- Brane -- Branko Čibej Director of Subversion | WANdisco | www.wandisco.com
