From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: is -1 really too "large" ?
Date: Mon, 21 Oct 2013 15:52:10 -0400 [thread overview]
Message-ID: <20131021195210.GA28909@redhat.com> (raw)
In-Reply-To: <52657514.3020707@gmx.de>
On Mon, Oct 21, 2013 at 08:40:20PM +0200, Toralf Förster wrote:
> 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 <davej@redhat.com>
> 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)
So NFS returned -EOVERFLOW. Not sure why it would do that, but I'm goingto guess it
came from nftw internally doing an lseek. lseek's man page suggests..
EOVERFLOW
The resulting file offset cannot be represented in an off_t.
64bit server and 32 bit client perhaps ?
Dave
next prev parent reply other threads:[~2013-10-21 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 18:40 is -1 really too "large" ? Toralf Förster
2013-10-21 19:52 ` Dave Jones [this message]
2013-10-21 20:39 ` Toralf Förster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131021195210.GA28909@redhat.com \
--to=davej@redhat.com \
--cc=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox