Linuxulator: syscall statfs64 not implemented?
Paul Mather
paul at gromit.dlib.vt.edu
Wed Aug 23 15:50:32 UTC 2006
On Mon, 2006-08-21 at 15:46 +0200, Divacky Roman wrote:
> > it seems like very trivial so expect patch today ;)
>
> www.stud.fit.vutbr.cz/~xdivac02/statfs64.patch
>
> pls tell me if this works, thnx
The patch applied and built on i386. However, when I run the resultant
kernel, the problem of the "syscall statfs64 not implemented" messages
goes away but my Tivoli backup still fails (in a different way). (The
same Tivoli client and setup worked on i386 -CURRENT prior to
mid-August, and currently is working on an i386 6.1-STABLE system.)
Now, when the scheduled backup runs, I get things like this in my
dsmerror.log:
08/23/06 02:58:37 TransErrno: Unexpected error from GetFSInfo:statfs, errno = 14
08/23/06 02:58:38 ANS1228E Sending of object '/backup' failed
08/23/06 02:58:38 ANS1063E The specified path is not a valid file system or logical volume name.
08/23/06 02:58:38 ANS1228E Sending of object '/backup/var' failed
08/23/06 02:58:38 ANS1063E The specified path is not a valid file system or logical volume name.
08/23/06 02:58:38 ANS1228E Sending of object '/backup/usr' failed
08/23/06 02:58:38 ANS1063E The specified path is not a valid file system or logical volume name.
08/23/06 02:58:40 ANS1512E Scheduled event 'DESKTOP_DAILY_BACKUP' failed. Return code = 12.
I don't know if this indicates that there is a problem with the
implementation of statfs64/statfs, now. (I don't know if it complicates
matters, but I'm backing up mounted snapshots.)
Cheers,
Paul.
--
e-mail: paul at gromit.dlib.vt.edu
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
--- Frank Vincent Zappa
More information about the freebsd-current
mailing list