[Bugs] [Bug 1452766] VM crashing but there's no apparent reason

bugzilla at redhat.com bugzilla at redhat.com
Wed Jul 26 16:07:09 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1452766

Mattia Lambertini <mattia.lambertini at m-iti.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mattia.lambertini at m-iti.org



--- Comment #6 from Mattia Lambertini <mattia.lambertini at m-iti.org> ---
I'm experiencing what it seems the same issue.

Gluster version is 3.10.3

My current setup is quite simple, I'm starting with just one node (it's planned
to add 2 more in the near future) and one volume with one brick:

Volume Name: gv0
Type: Distribute
Volume ID: ba11f016-3ae5-4fc2-b5a1-550bbcc74e39
Status: Started
Snapshot Count: 0
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: pr1-cluster:/data/brick1/gv0
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
diagnostics.brick-log-level: WARNING

Sharding is disabled.

>From the brick log:

[2017-07-26 15:49:05.765830] E [MSGID: 113107] [posix.c:1080:posix_seek]
0-gv0-posix: seek failed on fd 31 length 40273903616 [No such device or
address]
[2017-07-26 15:49:05.765883] E [MSGID: 115089]
[server-rpc-fops.c:2070:server_seek_cbk] 0-gv0-server: 16: SEEK-2
(c66abe5a-ff28-4e4b-8391-d9a3e7aa7838), client:
pr1-16895-2017/07/26-15:49:05:750324-gv0-client-0-0-0, error-xlator: gv0-posix
[No such device or address]
[2017-07-26 15:49:05.768248] E [MSGID: 113107] [posix.c:1080:posix_seek]
0-gv0-posix: seek failed on fd 31 length 53687091200 [No such device or
address]
[2017-07-26 15:49:05.768289] E [MSGID: 115089]
[server-rpc-fops.c:2070:server_seek_cbk] 0-gv0-server: 20: SEEK-2
(1f7a84d5-8383-41f0-8816-bfd55b105f9d), client:
pr1-16895-2017/07/26-15:49:05:750324-gv0-client-0-0-0, error-xlator: gv0-posix
[No such device or address]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list