[Ocfs2-users] mount failed with 'Device or resource busy'

Robin Lee robinlee.sysu at gmail.com
Mon Dec 23 22:29:27 PST 2019


On Fri, Dec 20, 2019 at 6:04 PM Robin Lee <robinlee.sysu at gmail.com> wrote:
>
> Hi,
>
> In an OCFS2 cluster with three XenServer 7.1.1 hosts, one of it failed
> to mount an OCFS2 FS.
> The kernel is based on Linux 4.4.27.
>
> mount output:
> mount.ocfs2: Device or resource busy while mounting /dev/sdb on
> /run/sr-mount/71ad344e-8c3e-0850-470f-6f625afbdb67. Check 'dmesg' for
> more information on this error.
>
> kernel messge:
> [  905.383687] scsi host5: iSCSI Initiator over TCP/IP
> [  905.398386] scsi 5:0:0:0: RAID              IET      Controller
>   0001 PQ: 0 ANSI: 5
> [  905.399358] scsi 5:0:0:0: Attached scsi generic sg2 type 12
> [  905.403517] scsi 5:0:0:1: Direct-Access     IET      VIRTUAL-DISK
>   0001 PQ: 0 ANSI: 5
> [  905.404757] sd 5:0:0:1: Attached scsi generic sg3 type 0
> [  905.410353] sd 5:0:0:1: [sdb] 20971520 512-byte logical blocks:
> (10.7 GB/10.0 GiB)
> [  905.410356] sd 5:0:0:1: [sdb] 4096-byte physical blocks
> [  905.411167] sd 5:0:0:1: [sdb] Write Protect is off
> [  905.411170] sd 5:0:0:1: [sdb] Mode Sense: 69 00 10 08
> [  905.411719] sd 5:0:0:1: [sdb] Write cache: enabled, read cache:
> enabled, supports DPO and FUA
> [  905.422200] sd 5:0:0:1: [sdb] Attached SCSI disk
> [  915.376485] o2net: Connected to node xxxserver-pool1 (num 0) at
> 192.168.58.206:7777
> [  915.381648] o2net: Connected to node xxxserver-pool2 (num 1) at
> 192.168.58.151:7777
> [  921.380352] o2net: No longer connected to node xxxserver-pool1 (num
> 0) at 192.168.58.206:7777
> [  921.382091] o2net: No longer connected to node xxxserver-pool2 (num
> 1) at 192.168.58.151:7777
> [  921.516900] sd 5:0:0:1: [sdb] Synchronizing SCSI cache
>
> The LUN is an iSCSI one.
>
> Rebooting the host does not help.
>
> What should I do to further investigate the issue?
>
> -robin
I found a multipath device is generated with sdb included, so directly
mounting sdb failed with device busy.
That's not a fault of OCFS2.

-robin



More information about the Ocfs2-users mailing list