| Re: Backup Strategy for Multiple VEs [message #27020 is a reply to message #23849] |
Thu, 07 February 2008 00:24   |
seanfulton
Messages: 105
Registered: May 2007
|
Senior Member |
|
|
Question for you:
I was able to use sshfs and vzdump to make backups, and it was fantastic.
Then I started getting corruption on the ext3 filesystem on one of my SATA drives (not over the sshfs connection, on another drive on the *client* machine).
The drive was purchased in may, two of them were actually, they are both running on different machines with different controllers and both are showing the same corruption issues.
The only things that appear to be in common are the host machine (SuperMicro servers), both are using the OpenVZ kernel (47 and 53), and both are using sshfs mounts. The problem only cropped up in the last couple of weeks (the 47 kernel has been around longer than that), so that's why I suspect something new, aka sshfs.
I did some research on ext3 errors in the 2.6.18 kernels and found various spurious issues with the kernel, but one comment someone made was that user-space filesystem drivers could lead to memory corruption that would cause ext3 errors. I'm thinking if it were the 2.6.18 kernel itself, there would be tons of reports on this forum.
Then I remembered your post and was wondering: did you get sshfs working? If so, any issues with the drives on your machine?
It's possible it could be an issue with the controllers, which while both different, are both cheap, SATA150 controllers hooked to SATA300 drives. If I can't find another solution, I'm going to swap the controllers out.
I just thought perhaps you may have run across something like this.
Anything?
sean
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
