GFS or GFS2 file system withdraws after temporary failure of all paths in multipath map in RHEL
Issue
- How can I avoid a GFS/GFS2 withdrawl when the paths in my multipath map go down for a short amount of time?
- Experienced a failure on the storage array which lead to all paths in the multipath device failing temporarily, and the GFS or GFS2 file system residing on it withdrew
Nov 20 01:59:12 node1 kernel: end_request: I/O error, dev dm-3, sector 0
Nov 20 01:59:12 node1 kernel: end_request: I/O error, dev dm-3, sector 4295039024
Nov 20 01:59:12 node1 kernel: __ratelimit: 12614 callbacks suppressed
Nov 20 01:59:12 node1 kernel: Buffer I/O error on device dm-5, logical block 8710
Nov 20 01:59:12 node1 kernel: lost page write due to I/O error on dm-5
Nov 20 01:59:12 node1 kernel: end_request: I/O error, dev dm-3, sector 9232768336
Nov 20 01:59:12 node1 kernel: GFS2: fsid=mycluster:gfs2.0: fatal: I/O error
Nov 20 01:59:12 node1 kernel: GFS2: fsid=mycluster:gfs2.0: block = 8710
Nov 20 01:59:12 node1 kernel: GFS2: fsid=mycluster:gfs2.0: function = log_write_header, file = fs/gfs2/log.c, line = 616
Nov 20 01:59:12 node1 kernel: GFS2: fsid=mycluster:gfs2.0: about to withdraw this file system
Nov 20 01:59:12 node1 kernel: end_request: I/O error, dev dm-3, sector 9232768336
Environment
- Red Hat Enterprise Linux (RHEL) 5 or 6 with the Resilient Storage Add On
- GFS or GFS2 file systems
- device-mapper-multipath
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.