is -1 really too "large" ?
Toralf Förster <[email protected]>
| Newsgroups | org.kernel.vger.trinity |
|---|---|
| Message-ID | <[email protected]> |
got today : run trinity at Mon Oct 21 20:38:27 CEST 2013 28#-1 M=/mnt/nfsv4 rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs0000000000004924000000cb': Device or resource busy rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs0000000000003fdd000000a9': Device or resource busy rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs00000000000034230000007a': Device or resource busy rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs0000000000002d320000006b': Device or resource busy rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs0000000000001a7c00000035': Device or resource busy rm: cannot remove '/mnt/nfsv4/victims/v1/v2/.nfs00000000000017600000002a': Device or resource busy Trinity v1.3pre Dave Jones <[email protected]> Done parsing arguments. Marking all syscalls as enabled. [init] Enabled 351 syscalls. Disabled 0 syscalls. [init] Using pid_max = 32768 [init] Started watchdog process, PID is 15311 [main] Main thread is alive. [main] Generating file descriptors [main] Something went wrong during nftw(/mnt/nfsv4/victims/v1/v2). (-1:Value too large for defined data type) [child2:15315] iopl (110) returned ENOSYS, marking as inactive. [child2:15315] acct (51) returned ENOSYS, marking as inactive. [child2:15315] perf_event_open (336) returned ENOSYS, marking as inactive. ... -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3