On 1/14/10 6:16 PM, Hauke Fath wrote:
All,
after upgrading a few i386 servers to netbsd-5, wip/tsm (5.2.2,
now 5.2.5)
terminates with an OOM error:
[...]
I also hit problems running the Veritas Netbackup client for Linux
after
upgrading to netbsd-5 (from netbsd-4).
Any idea what changes in COMPAT_LINUX shipped with netbsd-5 might be
responsible?
First, the suse(100)_base package has an "error" then running
netbsd-5,
since linking outside the emulation root is not permitted. See:
http://mail-index.netbsd.org/pkgsrc-users/2009/05/26/msg009936.html
The symlink /emul/linux/etc/mtab should point to /proc/mounts
instead of
/emul/linux/... The NetBackup client use /etc/mtab, which then
fails if
it isn't corrected.
Second, the filesystems never worked to backup unless they where
mounted
inside the emulation root. So I NFS-mounted them under
/emul/linux/netbackup/... instead.
However, the df command (which Netbackup also uses during backups)
shows
the real path (which is /usr/pkg/emul/...), so I mimiced the
directory
tree under /emul/linux/... (usr/pkg/emul/linux), and a netbackup
symlink
at the top, pointing back to /netbackup.
After that, we at least got a full backup to work, but the
incremental
backups still fails. It doesn't feel stable ATM. I just noticed
that the
df command seems to get "blocked" during a incremental backup try.