GFS/GFS2 withdraws, "attempt to access beyond end of device", I/O errors, and/or other filesystem-related problems after extending a cluster-shared LVM logical volume in RHEL 5, 6, or 7
Issue
- When I extend a clustered logical volume, I see I/O errors on some nodes afterwards.
- File system aborts or withdraws after extending logical volume in a cluster
- We added more storage to an existing cluster. Now that we have started actively loading the GFS file system with new data we sporadically get I/O errors on the file system
Sep 17 09:37:56 example kernel: attempt to access beyond end of device
Sep 17 09:37:56 example kernel: dm-68: rw=0, want=10359732256, limit=8388214784
- GFS or GFS2 file system withdrawls resulting from I/O errors following "attempt to access beyond end of device" errors
- Clustered logical volumes are missing on some nodes after creating them, or extending existing ones onto new physical volumes
Environment
- Red Hat Enterprise Linux (RHEL) 5, 6, 7 with the High Availability and/or Resilient Storage Add On
- LVM logical volumes shared across multiple cluster nodes
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
