AnsweredAssumed Answered

disksetup: Device or resource busy

Question asked by matt on Jun 24, 2012
Latest reply on Jun 25, 2012 by matt
I've looked through the previous disksetup questions, and while I think this issue is similar, I can't quite resolve it with the info from other questions.

I'm building a new 1.2.7 M3 cluster. First, I manually configured the cldb node and disksetup ran correctly on that. Next I moved on to set up the other two zookeeper nodes, but the disksetup step fails with the following:

    2012-06-25 00:26:04,8222 ERROR Global fs/server/util/mrconfig.cc:2411 clnt x.x.0.0:0 req 0 seq 0 InitDisk failed Device or resource busy.(16).
    InitDisk /dev/sdc
    InitDisk resp: status 16
    Disk init /dev/sdc failed. Error 16, Device or resource busy.

The /opt/mapr/logs/disksetup.log contains a few suspicious lines with the following:

    2012-06-25 00:41:12,801 3559 RunCmd:132 ERROR 2012-06-25 00:41:12,8002 ERROR Global fs/server/util/mrconfig.cc:306 clnt x.x.0.0:0 req 0 seq 0 ListDisks rpc failed Connection reset by peer.(104).
    2012-06-25 00:41:12,8004 ERROR Global fs/server/util/mrconfig.cc:2430 clnt x.x.0.0:0 req 0 seq 0 ListDisk failed Connection reset by peer.(104).

So, based on the content of similar questions, I checked /opt/mapr/logs/mfs.log, and found this similar entry, referring to my CLDB node (which I haven't started the warden on yet)

    2012-06-25 00:41:14,8234 ERROR Replication fs/server/common/cldbha.cc:321 clnt x.x.0.0:0 req 0 seq 0 Got error Connection reset by peer (104) while trying to register with CLDB <ip-removed>:7222
    2012-06-25 00:41:14,8282 INFO IOMgr fs/server/io/spserver.cc:435 clnt x.x.0.0:0 req 0 seq 0 > InitDisk /dev/sdc ctx 0x3702940
    2012-06-25 00:41:14,8282 ERROR IOMgr fs/server/io/lun.cc:576 clnt x.x.0.0:0 req 0 seq 0 target device open(/dev/sdc) error Device or resource busy failed(errno 16)
    2012-06-25 00:41:14,8282 ERROR IOMgr fs/server/io/config.cc:105 clnt x.x.0.0:0 req 0 seq 0 OnlineDisk(/dev/sdc) failed Device or resource busy.(16)

However, accoring to 'lsof | grep sdc' nothing is using the device. Any suggestions on how I figure out why disksetup is reporting the device is busy when it otherwise does not appear to be busy?

Outcomes