loop device not matching file size

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











up vote
0
down vote

favorite












I have a sparse backing file (made via dd seek=) that's a partial image of a damaged disk. The size as given by ls matches the original disk. However, when looping it, /proc/partitions shows it as about have the size as the original disk. It seems like losetup is ignoring the final sparse extend of the file because it has no data following it.



As a result, if I use losetup -P (or kpartx) the partitioning fails on a partition extending past the size given by /proc/partitions.



How can I resolve this without expanding the file? (Perhaps writing to the last sector will help, but I would like to avoid touching the image).










share|improve this question

























    up vote
    0
    down vote

    favorite












    I have a sparse backing file (made via dd seek=) that's a partial image of a damaged disk. The size as given by ls matches the original disk. However, when looping it, /proc/partitions shows it as about have the size as the original disk. It seems like losetup is ignoring the final sparse extend of the file because it has no data following it.



    As a result, if I use losetup -P (or kpartx) the partitioning fails on a partition extending past the size given by /proc/partitions.



    How can I resolve this without expanding the file? (Perhaps writing to the last sector will help, but I would like to avoid touching the image).










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a sparse backing file (made via dd seek=) that's a partial image of a damaged disk. The size as given by ls matches the original disk. However, when looping it, /proc/partitions shows it as about have the size as the original disk. It seems like losetup is ignoring the final sparse extend of the file because it has no data following it.



      As a result, if I use losetup -P (or kpartx) the partitioning fails on a partition extending past the size given by /proc/partitions.



      How can I resolve this without expanding the file? (Perhaps writing to the last sector will help, but I would like to avoid touching the image).










      share|improve this question













      I have a sparse backing file (made via dd seek=) that's a partial image of a damaged disk. The size as given by ls matches the original disk. However, when looping it, /proc/partitions shows it as about have the size as the original disk. It seems like losetup is ignoring the final sparse extend of the file because it has no data following it.



      As a result, if I use losetup -P (or kpartx) the partitioning fails on a partition extending past the size given by /proc/partitions.



      How can I resolve this without expanding the file? (Perhaps writing to the last sector will help, but I would like to avoid touching the image).







      partition dd loop-device disk-image sparse-files






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 17 mins ago









      afuna

      1676




      1676

























          active

          oldest

          votes











          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%2f477818%2floop-device-not-matching-file-size%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477818%2floop-device-not-matching-file-size%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

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

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?