Re: 3.1.3 crash on volume start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As described it's a basic five node distribute:
Volume Name: distribute
Type: Distribute
Status: Created
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: store0:/data_testvol2
Brick2: store2:/data_testvol2
Brick3: sotre3:/data_testvol2
Brick4: store4:/data_testvol2
Brick5: store5:/data_testvol2

Client logs are nothing special because it can't connect as the server has crashed already: "failed to get the port number for remote subvolume". Server logs for 3.1.3 were attached previously, nothing changed in 3.1.4qa4.

The qa release attempt was precisely because the stable 3.1.3 crashes.

On 04/12/2011 04:36 PM, Lakshmipathi.G wrote:
Hi -
I'm going to probably give a 3.1 (qa4) and/or 3.2 (qa11) release a try
Please try with stable version(3.1.x) instead of (3.1.xQAx) QA releases.
Also provide the output of command - "gluster volume info" along with server and client logs.





[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux