device-mapper: reload ioctl on cache1 failed: Device or resource busy

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












When I run the below command while setting up dm-cache on my CentOS system, I receive the error:



device-mapper: reload ioctl on cache1 failed: Device or resource busy
Command failed


Command is:



dmsetup create 'cache1' --table '0 195309568 cache /dev/sdb /dev/sda 512 1 writethrough default 0'


Does anyone have idea about this error or have faced this error while setting up dm-cache?



My dmesg output is



[1907480.058991] device-mapper: table: 253:3: cache: Error opening metadata device
[1907480.058996] device-mapper: ioctl: error adding target to table









share|improve this question



























    up vote
    1
    down vote

    favorite












    When I run the below command while setting up dm-cache on my CentOS system, I receive the error:



    device-mapper: reload ioctl on cache1 failed: Device or resource busy
    Command failed


    Command is:



    dmsetup create 'cache1' --table '0 195309568 cache /dev/sdb /dev/sda 512 1 writethrough default 0'


    Does anyone have idea about this error or have faced this error while setting up dm-cache?



    My dmesg output is



    [1907480.058991] device-mapper: table: 253:3: cache: Error opening metadata device
    [1907480.058996] device-mapper: ioctl: error adding target to table









    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      When I run the below command while setting up dm-cache on my CentOS system, I receive the error:



      device-mapper: reload ioctl on cache1 failed: Device or resource busy
      Command failed


      Command is:



      dmsetup create 'cache1' --table '0 195309568 cache /dev/sdb /dev/sda 512 1 writethrough default 0'


      Does anyone have idea about this error or have faced this error while setting up dm-cache?



      My dmesg output is



      [1907480.058991] device-mapper: table: 253:3: cache: Error opening metadata device
      [1907480.058996] device-mapper: ioctl: error adding target to table









      share|improve this question















      When I run the below command while setting up dm-cache on my CentOS system, I receive the error:



      device-mapper: reload ioctl on cache1 failed: Device or resource busy
      Command failed


      Command is:



      dmsetup create 'cache1' --table '0 195309568 cache /dev/sdb /dev/sda 512 1 writethrough default 0'


      Does anyone have idea about this error or have faced this error while setting up dm-cache?



      My dmesg output is



      [1907480.058991] device-mapper: table: 253:3: cache: Error opening metadata device
      [1907480.058996] device-mapper: ioctl: error adding target to table






      linux centos cache device-mapper






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 19 '16 at 0:02









      Jeff Schaller

      32.6k849110




      32.6k849110










      asked Apr 18 '16 at 23:08









      arpit joshi

      1901312




      1901312




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The cache target requires 3 devices, but you have only specified two. I believe the devices also must be dm devices, not a scsi disk.






          share|improve this answer




















          • well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
            – arpit joshi
            Apr 19 '16 at 0:00










          • @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
            – psusi
            Apr 19 '16 at 1:59










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f277394%2fdevice-mapper-reload-ioctl-on-cache1-failed-device-or-resource-busy%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          The cache target requires 3 devices, but you have only specified two. I believe the devices also must be dm devices, not a scsi disk.






          share|improve this answer




















          • well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
            – arpit joshi
            Apr 19 '16 at 0:00










          • @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
            – psusi
            Apr 19 '16 at 1:59














          up vote
          0
          down vote













          The cache target requires 3 devices, but you have only specified two. I believe the devices also must be dm devices, not a scsi disk.






          share|improve this answer




















          • well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
            – arpit joshi
            Apr 19 '16 at 0:00










          • @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
            – psusi
            Apr 19 '16 at 1:59












          up vote
          0
          down vote










          up vote
          0
          down vote









          The cache target requires 3 devices, but you have only specified two. I believe the devices also must be dm devices, not a scsi disk.






          share|improve this answer












          The cache target requires 3 devices, but you have only specified two. I believe the devices also must be dm devices, not a scsi disk.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 18 '16 at 23:43









          psusi

          13.2k22439




          13.2k22439











          • well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
            – arpit joshi
            Apr 19 '16 at 0:00










          • @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
            – psusi
            Apr 19 '16 at 1:59
















          • well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
            – arpit joshi
            Apr 19 '16 at 0:00










          • @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
            – psusi
            Apr 19 '16 at 1:59















          well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
          – arpit joshi
          Apr 19 '16 at 0:00




          well the cache is the name of the cache and /dev/sdb(cache device ,ssd) and /dev/sda(my hardisk ,source device) .Am i missing something here?
          – arpit joshi
          Apr 19 '16 at 0:00












          @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
          – psusi
          Apr 19 '16 at 1:59




          @asj177, according to Documentation/device-mapper/cache.txt in the linux kernel sources, the cache target takes <metadata dev> <cache dev> <origin dev>.
          – psusi
          Apr 19 '16 at 1:59

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f277394%2fdevice-mapper-reload-ioctl-on-cache1-failed-device-or-resource-busy%23new-answer', 'question_page');

          );

          Post as a guest













































































          Mlz kDTVmnATOjXDk,YSgx0DIA7DG KzeMgsvYreC,mnvHc
          KWWRO6zadb RFnJPOy,OfqMauf51DxRi61HetQqEXHXmaJxBoXgmSZEK V,Xys

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          How many registers does an x86_64 CPU actually have?

          Displaying single band from multi-band raster using QGIS