We have a couple of volumes that cannot be backed up, and cannot be moved. When you do a vos move, it fails during the dump, and VolserLog report: Volser: DumpFile: Error reading inode 26841 for vnode 20; null padding file There are also some disk errors reported at the same time. The files within the volume, however, look just fine. This happened once before. In that case shutting down fs and running fsck fixed some of the volumes. The others were moved to new volumes using the up command. (The disk was also replaced.) Any ideas on what causes this, and how to get around it? Thanks, -- Michael D. Sofka [EMAIL PROTECTED] ITS Systems Programmer TeX, AFS, NIS, NTP, Astronomy, Skepticism. Rensselaer Polytechnic Institute, Troy, NY. http://www.rpi.edu/~sofkam/
