Hi Les,
On Wed, Dec 4, 2013 at 4:31 PM, Pat Haley <pha...@mit.edu> wrote:
How about 'svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper'?
No, that also fails
mseas(MeanAvg)% svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper
svnadmin: disk I/O error
svnadmin: disk I/O error
So, I'm guessing it's a disk error...
If it is, it's a mighty peculiar one:
(1) We have many other files & directories (including all of
our user areas) and nothing else is coming up with errors
(2) These different svn repositories are in widely disparate
locations under our directory trees, yet all are giving
similar errors.
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?
Also, does the NAS physically holding the disks have any logging
facility where you could see physical disk errors reported?
I looked in /var/log, but none of the files had any
messages at the times I did the above tests.
It if is a generic linux box 'dmesg' might show it. If it is some
dedicated file server you'll have to find its own diagnostic
procedures.
It is a generic linux box. However doing dmesg before and
after generating an svn error doesn't show anything new.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Pat Haley Email: pha...@mit.edu
Center for Ocean Engineering Phone: (617) 253-6824
Dept. of Mechanical Engineering Fax: (617) 253-8125
MIT, Room 5-213 http://web.mit.edu/phaley/www/
77 Massachusetts Avenue
Cambridge, MA 02139-4301
