Re: [ClusterLabs] lvm on shared storage and a lot of...

2017-04-25 Thread lejeczek



On 18/04/17 15:40, Ken Gaillot wrote:

On 04/18/2017 09:14 AM, lejeczek wrote:


On 18/04/17 14:45, Digimer wrote:

On 18/04/17 07:31 AM, lejeczek wrote:

.. device_block & device_unblock in dmesg.

and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to spot a pattern.

Shared storage is a sas3 enclosure.
I believe I follow docs on LVM to the letter. I don't know what could be
the problem.

would you suggest ways to troubleshoot it? Is it faulty/failing hardware?

many thanks,
L.

LVM or clustered LVM?


no clvmd
And inasmuch as the resource would start, fs would mount, if I start
using it more intensely I'd get more of block/unblock and after a while
mountpoint resource failes and then LVM resource too.
It gets only worse after, even after I deleted resourced, I begin to
see, eg.:

[ 6242.606870] sd 7:0:32:0: device_unblock and setting to running,
handle(0x002c)
[ 6334.248617] sd 7:0:18:0: [sdy] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 6334.248633] sd 7:0:18:0: [sdy] tag#0 Sense Key : Not Ready [current]
[ 6334.248640] sd 7:0:18:0: [sdy] tag#0 Add. Sense: Logical unit is in
process of becoming ready

This feels like a hardware issue to me. Have you checked the SMART data
on the drives?


[ 6334.248647] sd 7:0:18:0: [sdy] tag#0 CDB: Read(10) 28 00 00 00 00 00
00 00 08 00
[ 6334.248652] blk_update_request: I/O error, dev sdy, sector 0


for those who might experience similar - make sure your 
controller+enclosure fully support mix of SAS, 
otherwise... there will be trouble :)



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] lvm on shared storage and a lot of...

2017-04-19 Thread lejeczek



On 18/04/17 15:40, Ken Gaillot wrote:

On 04/18/2017 09:14 AM, lejeczek wrote:


On 18/04/17 14:45, Digimer wrote:

On 18/04/17 07:31 AM, lejeczek wrote:

.. device_block & device_unblock in dmesg.

and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to spot a pattern.

Shared storage is a sas3 enclosure.
I believe I follow docs on LVM to the letter. I don't know what could be
the problem.

would you suggest ways to troubleshoot it? Is it faulty/failing hardware?

many thanks,
L.

LVM or clustered LVM?


no clvmd
And inasmuch as the resource would start, fs would mount, if I start
using it more intensely I'd get more of block/unblock and after a while
mountpoint resource failes and then LVM resource too.
It gets only worse after, even after I deleted resourced, I begin to
see, eg.:

[ 6242.606870] sd 7:0:32:0: device_unblock and setting to running,
handle(0x002c)
[ 6334.248617] sd 7:0:18:0: [sdy] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 6334.248633] sd 7:0:18:0: [sdy] tag#0 Sense Key : Not Ready [current]
[ 6334.248640] sd 7:0:18:0: [sdy] tag#0 Add. Sense: Logical unit is in
process of becoming ready

This feels like a hardware issue to me. Have you checked the SMART data
on the drives?



I did think that, there is something unsettling about that 
hardware I use, specifically the enclosure.


But today I gotten rid of the cluster and enclosure is 
currently linked to only one box, single link, and it is 
quiet so far... gee..




[ 6334.248647] sd 7:0:18:0: [sdy] tag#0 CDB: Read(10) 28 00 00 00 00 00
00 00 08 00
[ 6334.248652] blk_update_request: I/O error, dev sdy, sector 0

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] lvm on shared storage and a lot of...

2017-04-18 Thread lejeczek



On 18/04/17 14:45, Digimer wrote:

On 18/04/17 07:31 AM, lejeczek wrote:

.. device_block & device_unblock in dmesg.

and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to spot a pattern.

Shared storage is a sas3 enclosure.
I believe I follow docs on LVM to the letter. I don't know what could be
the problem.

would you suggest ways to troubleshoot it? Is it faulty/failing hardware?

many thanks,
L.

LVM or clustered LVM?


no clvmd
And inasmuch as the resource would start, fs would mount, if 
I start using it more intensely I'd get more of 
block/unblock and after a while mountpoint resource failes 
and then LVM resource too.
It gets only worse after, even after I deleted resourced, I 
begin to see, eg.:


[ 6242.606870] sd 7:0:32:0: device_unblock and setting to 
running, handle(0x002c)
[ 6334.248617] sd 7:0:18:0: [sdy] tag#0 FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6334.248633] sd 7:0:18:0: [sdy] tag#0 Sense Key : Not 
Ready [current]
[ 6334.248640] sd 7:0:18:0: [sdy] tag#0 Add. Sense: Logical 
unit is in process of becoming ready
[ 6334.248647] sd 7:0:18:0: [sdy] tag#0 CDB: Read(10) 28 00 
00 00 00 00 00 00 08 00

[ 6334.248652] blk_update_request: I/O error, dev sdy, sector 0


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] lvm on shared storage and a lot of...

2017-04-18 Thread Digimer
On 18/04/17 07:31 AM, lejeczek wrote:
> .. device_block & device_unblock in dmesg.
> 
> and I see that the LVM resource would fail.
> This to me seems to happen randomly, or I fail to spot a pattern.
> 
> Shared storage is a sas3 enclosure.
> I believe I follow docs on LVM to the letter. I don't know what could be
> the problem.
> 
> would you suggest ways to troubleshoot it? Is it faulty/failing hardware?
> 
> many thanks,
> L.

LVM or clustered LVM?

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


[ClusterLabs] lvm on shared storage and a lot of...

2017-04-18 Thread lejeczek

.. device_block & device_unblock in dmesg.

and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to spot a 
pattern.


Shared storage is a sas3 enclosure.
I believe I follow docs on LVM to the letter. I don't know 
what could be the problem.


would you suggest ways to troubleshoot it? Is it 
faulty/failing hardware?


many thanks,
L.

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org