On Wed, Dec 4, 2013 at 7:09 PM, Pat Haley <[email protected]> wrote:
>
>> One thing that didn't stand out in my original Email was the reason
> for the reboot. We turned quotas on. Would svn react poorly
> to this?
Only on a write that exceeds quota.
> It is a generic linux box. However doing dmesg before and
> after generating an svn error doesn't show anything new.
Can you run the svnadmin verify on the box with the drives? Maybe it
is just a client/network/mount issue and the things that worked (ls,
etc.) were running from cache. Can you unmount/mount or reboot a
client?
--
Les Mikesell
[email protected]
